CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

migrate-to-skills

Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use when you want to migrate rules or commands to skills, convert .mdc rules to SKILL.md format, or consolidate commands into the skills directory.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills-cursor/migrate-to-skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete before/after templates, exact paths, and clear parallel-subagent workflow structure, but it is held back by triply-repeated conversion procedures and the absence of any verification step before destructively deleting original files. Consolidating the duplicated sections and gating deletion on a verification pass would raise both conciseness and workflow clarity.

Suggestions

Add an explicit verification step (e.g., re-read each generated SKILL.md and confirm frontmatter plus verbatim body) before deleting original files, replacing the current per-file 'Delete the original' instruction that runs without any check.

Deduplicate the conversion instructions: the 'Conversion Format' examples, the 'Migrate a Rule/Command' step lists, and the Workflow section all restate the same procedure — state it once and reference it from the workflow.

Reconcile the command description guidance: step 2 says to extract the description from the first heading, but the example infers a richer description ('Commit current work with standardized message format') — pick one rule and make the example match it.

DimensionReasoningScore

Conciseness

The verbatim-preservation instruction appears twice ("Do not modify, reformat, or 'improve' it - copy verbatim" and "Copy the body content character-for-character"), and the rule/command conversion procedure is repeated three times (Conversion Format examples, the numbered step lists, and the Workflow section) — more than minor tightening needed.

3 / 5

Actionability

Concrete before/after SKILL.md examples, exact glob patterns ("{workspaceFolder}/**/.cursor/rules/*.mdc"), and exact destination paths make the guidance mostly executable; a minor inconsistency (the command example shows description "Commit current work with standardized message format" while step 2 says "Extract description from the first heading") leaves a small gap.

4 / 5

Workflow Clarity

Sequences are clearly listed with checklists, parallel subagent dispatch, and an undo path, but this is a destructive batch operation (originals deleted per-file in steps VI/5/6) with no verification before deletion — "verifying migration works" appears only as an optional note, so the destructive-batch cap applies.

3 / 5

Progressive Disclosure

No bundle files exist and sections are well organized (Locations table, Conversion Format, Notes, Workflow) with no buried references; however, at ~125 lines the two near-duplicate workflow paths (with and without the Task tool) could be consolidated, which is a minor organization gap.

4 / 5

Total

14

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it states a clear, concrete capability with exact file paths and formats, and provides an explicit 'Use when' clause with multiple natural trigger phrases. It occupies a distinct niche (Cursor rules/command migration) with essentially no conflict risk. The only minor gaps are limited action variety and a few missing synonyms in trigger terms.

DimensionReasoningScore

Specificity

"Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/)" names concrete actions with exact source paths and extensions, but coverage centers on a single convert/migrate action with variants rather than the multiple distinct actions of a 5.

4 / 5

Completeness

Explicitly answers both: what ("Convert ... Cursor rules ... and slash commands ... to Agent Skills format") and when ("Use when you want to migrate rules or commands to skills, convert .mdc rules to SKILL.md format, or consolidate commands into the skills directory") with three concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural trigger phrases like "migrate rules or commands to skills", "convert .mdc rules to SKILL.md format", and "consolidate commands into the skills directory" give good keyword coverage including file extensions, though common synonyms such as "port" or "move my rules" are missing.

4 / 5

Distinctiveness Conflict Risk

Highly niche triggers ("Cursor rules", ".cursor/rules/*.mdc", ".cursor/commands/*.md", ".mdc") make it clearly distinguishable from other skills with minimal risk of triggering for the wrong skill.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

saski/arnesto

Path

.cursor/skills-cursor/migrate-to-skills/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.