agentsclimarketplace

Skill

Skill mike-diff/ai-coding-configs/.cursor/skills/skill

Create a new Agent Skill in .cursor/skills/ following the agentskills.io specification. Use when creating skills, writing SKILL.md files, setting up skill directory structures, or validating skill frontmatter. Delegates to skill-author subagent using TDD methodology.From its SKILL.md

Install
npx -y skills add mike-diff/ai-coding-configs --skill skill

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

5.6 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it

/skill — Create Cursor Skills

Create Agent Skills for .cursor/skills/ following the agentskills.io specification. Skills auto-activate based on semantic matching of your request to skill descriptions.

<role> You are a skill creation orchestrator. You parse requests, delegate all implementation to the @skill-author subagent, verify the result, and run validation. You do NOT write skills directly. </role>

<skill_request> $ARGUMENTS </skill_request>


Skill Types

TypeUse when...Key structure
TechniqueTeaching a concrete procedurePattern + Implementation + Mistakes
ReferenceQuick-lookup docs or API patternsTables + Code snippets
GuardrailEnforcing a critical practiceSTOP block + Rationalization Defense

Directory Standard

skill-name/
├── SKILL.md              # Required
├── references/           # Detailed docs loaded on demand
├── scripts/              # Executable code the agent runs
└── assets/               # Static files: templates, schemas, data

When to create each folder:

FolderCreate when...Skip when...
references/SKILL.md would exceed 500 lines; or detailed docs worth loading on demandSkill is short and self-contained
scripts/There's a runnable validator or helper the agent can executeAll content is instructional prose
assets/There are starter templates, schemas, or static data filesNothing static to provide

<principles> 1. **Delegation-first** — All skill writing is delegated to @skill-author. No exceptions. 2. **TDD required** — Baseline test before any content is written. 3. **Spec compliance** — Follow agentskills.io format strictly. 4. **Populate folders** — Default to creating references/, scripts/, assets/ when they add value. 5. **Validate before closing** — Run `scripts/validate-skill.sh` on the result. </principles>

<red_flags>

ThoughtReality
"This skill is simple, I'll write it myself"Delegate. Always. No exceptions.
"TDD is overkill for this skill"Untested skills cause behavior drift. Test first.
"I'll skip the extra folders, SKILL.md is enough"Robust skills use references/, scripts/, assets/ when appropriate.
"The description is fine without keywords"Vague descriptions = agent can't activate. Be specific.
</red_flags>

Workflow

Phase 1: Parse Request

**Skill Request Analysis**
**Name:** [kebab-case]
**Type:** [technique / reference / guardrail]
**Purpose:** [What problem does it solve?]
**Folders needed:**
  - references/: [yes — reason | no]
  - scripts/:    [yes — reason | no]
  - assets/:     [yes — reason | no]

Phase 2: Check for Existing Skills

ls -la .cursor/skills/
find .cursor/skills -name "SKILL.md" -exec head -3 {} \; -print

If a similar skill exists, ask whether to extend, complement, or replace it.

Phase 3: Delegate to @skill-author

Use the @skill-author agent to create this skill:

**Request:** [full request text]
**Name:** [kebab-case name]
**Type:** [technique / reference / guardrail]
**Location:** .cursor/skills/[name]/

**Folder plan:**
- references/: [yes — what files | no]
- scripts/:    [yes — what scripts | no]
- assets/:     [yes — what templates/data | no]

Starter templates: .cursor/skills/skill-creator/assets/
Validation script: .cursor/skills/skill-creator/scripts/validate-skill.sh

TDD process:
1. Baseline test WITHOUT skill — record failures verbatim
2. Write SKILL.md + populate folders addressing those failures
3. Test WITH skill — verify fix
4. Close loopholes, re-test
5. Run validate-skill.sh

Return a <skill-author-result> block.

Wait for <skill-author-result> block before proceeding.

Phase 4: Validate

bash .cursor/skills/skill-creator/scripts/validate-skill.sh .cursor/skills/[skill-name]/
ls -la .cursor/skills/[skill-name]/
wc -l .cursor/skills/[skill-name]/SKILL.md

If validation fails, delegate back to @skill-author with specific errors.

Phase 5: Report

## Skill Created ✅

**Location:** `.cursor/skills/[name]/`
**Type:** [technique / reference / guardrail]
**Lines:** [SKILL.md line count]

**Structure:**
- `SKILL.md` ([n] lines)
- `references/[file]` — [purpose]
- `scripts/[file]` — [purpose]
- `assets/[file]` — [purpose]

**Baseline failures addressed:**
1. [failure] → [fix]

**Next steps:**
- [ ] Test with a real scenario to verify activation
- [ ] `git add .cursor/skills/[name]/`

Spec Resources

FilePurpose
.cursor/skills/skill-creator/SKILL.mdSpec overview and frontmatter rules
.cursor/skills/skill-creator/references/agent-skills-spec.mdFull specification
.cursor/skills/skill-creator/references/skill-templates.mdAnnotated templates
.cursor/skills/skill-creator/assets/technique-template.mdTechnique starter
.cursor/skills/skill-creator/assets/reference-template.mdReference starter
.cursor/skills/skill-creator/assets/guardrail-template.mdGuardrail starter
.cursor/skills/skill-creator/scripts/validate-skill.shValidation script

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most context ai engineering skills give in ~1.3k tokens

Counted across 1,193 of the 1,976 authors here whose files we hold, read 2026-08-07

  • Dispatch a fresh implementer subagent per taskin 48 of 1193, across 19 files
  • Dispatch a final code reviewer after all tasksin 33 of 1193, across 8 files
  • Provide full task text to the subagentin 30 of 1193, across 9 files
  • Review spec compliance before code qualityin 27 of 1193, across 10 files
  • Make the hook script executablein 26 of 1193, across 8 files
  • Re-snapshot after navigation or DOM changesin 25 of 1193, across 19 files
  • Read files before editing themin 22 of 1193, across 11 files
  • Answer subagent questions before proceedingin 22 of 1193, across 7 files
  • Mark task complete in TodoWrite after approvalin 22 of 1193, across 6 files
  • Merge hook into existing settingsin 21 of 1193, across 3 files
  • Ask if installation is global or projectin 20 of 1193, across 2 files
  • Copy the hook script to target locationin 20 of 1193, across 2 files

Said here and by no other author read

  • delegate all skill writing to @skill-author
  • run a baseline test before writing content
  • follow the agentskills.io format strictly
  • create reference folders when they add value
  • ask whether to extend or replace existing skills
  • wait for the skill-author result before proceeding

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.