mkalhitti-cloud/universal-or-strategy

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.