home / skills / mkalhitti-cloud / universal-or-strategy / audit-and-add-project-skills

audit-and-add-project-skills skill

/.cursor/skills/audit-and-add-project-skills

This skill audits project and Codex skills for Cursor compatibility and guides adding them to the workspace.

npx playbooks add skill mkalhitti-cloud/universal-or-strategy --skill audit-and-add-project-skills

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.3 KB
---
name: audit-and-add-project-skills
description: Audits project skills in .agent/skills/ and Codex skills for Cursor compatibility, then helps add compatible skills to .cursor/skills/. Use when the user wants to migrate project skills to Cursor, check if skills work with Cursor, or add existing skills to Cursor.
---

# Audit and Add Project Skills to Cursor

This skill scans project and Codex skills, checks Cursor compatibility, and guides adding them to Cursor.

## Skill Sources

| Source | Path | Notes |
|--------|------|-------|
| Project skills | `{workspaceFolder}/.agent/skills/*/SKILL.md` | Often Codex/Claude format |
| Codex skills | `~/.codex/skills/**/SKILL.md` | May need adaptation |

## Cursor Skill Format (Required)

Cursor expects:

```markdown
---
name: skill-name
description: What the skill does and when to use it (third person, specific)
---
# Title
Body...
```

### Compatibility Checklist

- [ ] **name**: Lowercase, hyphens only, max 64 chars
- [ ] **description**: Third person, includes WHAT and WHEN (trigger terms)
- [ ] **Body**: Markdown instructions (procedures, examples, workflows)

### Fields Cursor Ignores (OK to Keep)

- `license`, `metadata`, `disable-model-invocation`, `globs`, `alwaysApply`
- Codex-specific: `metadata.short-description`, `agents/openai.yaml` references

### Adaptation Notes

| Project/Codex Pattern | Cursor Equivalent |
|-----------------------|-------------------|
| `${PROJECT_ROOT}` | `{workspaceFolder}` or omit |
| `${BRAIN}`, `${HANDS}` | Omit or replace with "the agent" |
| References to "Codex" or "Claude" | Replace with "the agent" or "Cursor" |
| `~/.codex/skills/` paths | Use project `.cursor/skills/` or `~/.cursor/skills/` |

## Audit Workflow

1. **Discover skills**: List SKILL.md files in `.agent/skills/` and optionally `~/.codex/skills/`
2. **Read each SKILL.md**: Extract frontmatter (name, description)
3. **Validate**: Check name format, description quality, required structure
4. **Report**:
   - ✅ Compatible as-is
   - ⚠️ Compatible with minor edits (update description, fix name)
   - ❌ Needs adaptation (Codex-specific content, missing fields)

## Add-to-Cursor Workflow

**Target**: Project skills → `.cursor/skills/{skill-name}/`

1. Create `.cursor/skills/` if it doesn't exist
2. For each compatible skill:
   - Create `.cursor/skills/{skill-name}/`
   - Copy `SKILL.md` (and optional `reference.md`, `scripts/` if present)
   - Apply adaptations from audit (description, path refs)
3. Preserve original `.agent/skills/`—do not delete

**Do NOT** add skills to `~/.cursor/skills-cursor/`. That directory is reserved for Cursor built-in skills.

## Quick Commands

**List project skills:**
```
Get-ChildItem -Path ".agent/skills" -Directory | ForEach-Object { $_.Name }
```

**Check if SKILL.md exists:**
```
Test-Path ".agent/skills/{skill-name}/SKILL.md"
```

**Copy a skill to Cursor:**
```
Copy-Item -Path ".agent/skills/{skill-name}" -Destination ".cursor/skills/{skill-name}" -Recurse
```

## Decision: Project vs Personal

- **Project** (`.cursor/skills/`): Skills shared with the repo; available only in this workspace
- **Personal** (`~/.cursor/skills/`): Skills for all your projects

Use project scope for workspace-specific skills (NinjaTrader, UniversalOR, etc.). Use personal for generic skills (pdf, docx, code-formatter).

Overview

This skill audits project skills in .agent/skills/ and personal Codex skill locations for Cursor compatibility, then helps add compatible skills into .cursor/skills/ within the workspace. It verifies naming, description quality, and required structure, and applies minimal adaptations so skills run reliably under Cursor. Use it to migrate, validate, or install skills into a workspace-scoped Cursor skills folder.

How this skill works

The tool discovers skill documents under .agent/skills/ and optional Codex locations, reads each skill's frontmatter and body, and validates name format, description clarity, and Markdown structure required by Cursor. It classifies each skill as compatible, compatible with minor edits, or needing adaptation, and then copies compatible skills into .cursor/skills/{skill-name}/ while applying necessary path and reference fixes. Original project skills are preserved and personal skill directories are treated as separate targets.

When to use it

  • You want to migrate workspace skills into Cursor for a project-specific setup.
  • You need to check whether existing skills will run unchanged under Cursor.
  • You have Codex-format skills that may require adaptation for Cursor.
  • You want to add compatible skills into the workspace-scoped .cursor/skills/ folder.
  • You need a reproducible audit report before committing skill changes.

Best practices

  • Keep skill names lowercase with hyphens and under 64 characters for Cursor compatibility.
  • Write third-person descriptions that state WHAT the skill does and WHEN to use it (trigger terms).
  • Replace engine-specific references (Codex/Claude) with neutral wording like "the agent" or "Cursor".
  • Preserve the original project skill files; copy into .cursor/skills/ rather than moving or deleting.
  • Prefer workspace scope (.cursor/skills/) for repo-specific tools and personal scope (~/.cursor/skills/) for reusable, cross-project utilities.

Example use cases

  • Audit an automated trading skillset for NinjaTrader and add compatible tools into the workspace Cursor skills folder.
  • Scan a developer workspace for Codex-style skills, adapt descriptions and path variables, and install those marked compatible-with-minor-edits.
  • Create a reproducible package of workspace skills to share with collaborators by consolidating compatible skills into .cursor/skills/.
  • Validate naming and documentation for a batch of skills before including them in CI or workspace setup scripts.

FAQ

Will this delete my original project skills?

No. The workflow copies adapted skills into .cursor/skills/ and leaves the original project files intact.

Can it convert engine-specific references automatically?

Yes — common patterns (project root variables, references to Codex/Claude) are replaced or removed, but review is recommended for edge cases.

Where should I put widely reused utilities?

Place reusable tools in your personal skills folder (~/.cursor/skills/) and workspace-specific skills in .cursor/skills/ for repository-scoped availability.