Claude Cursor Skill

skill-authoring

Create or improve a skill: decide whether a skill is the right home, interview the user, write a brief SKILL.md, test it on real tasks and iterate. Load when asked to create a skill, turn team knowledge into one, or move a command into one.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download goldziher-ai-rulez-internal_builtins_universal_ai-governance_skills_skill-authoring-ca967ad.zip · 0 KB

goldziher/ai-rulez 162 16 forks MIT Updated 5h ago

Part of goldziher/ai-rulez — 151 skills

Install

skills CLI

npx skills add https://github.com/Goldziher/ai-rulez/tree/main/internal/builtins/universal/ai-governance/skills/skill-authoring

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install goldziher-ai-rulez@llmmart

Git git clone https://github.com/Goldziher/ai-rulez.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole goldziher/ai-rulez collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Check a skill is the right home before writing one (see config-placement).
name equals the directory name and is unique across the project. The description says what the skill does and when to use it, with the key terms a user or model would match on.
Keep the body brief and imperative, 50 to 150 lines. Move bulk to references/*.md and link it relatively.
Explore first. Check that every path, command and flag you cite exists. Do not repeat what a rule already says.
Self-review for length, repetition, contradictions and unverified claims.
Test on two or three real tasks. After each, ask what guidance was followed, what had to be explained by hand and where instructions contradict. Apply the fixes and test again.

Files (ai-rulez)

SKILL.md 1 KB

---
name: skill-authoring
description: "Create or improve a skill: decide whether a skill is the right home, interview the user, write a brief SKILL.md, test it on real tasks and iterate. Load when asked to create a skill, turn team knowledge into one, or move a command into one."
---

- Check a skill is the right home before writing one (see `config-placement`).
- `name` equals the directory name and is unique across the project. The `description` says what the skill does and when to use it, with the key terms a user or model would match on.
- Keep the body brief and imperative, 50 to 150 lines. Move bulk to `references/*.md` and link it relatively.
- Explore first. Check that every path, command and flag you cite exists. Do not repeat what a rule already says.
- Self-review for length, repetition, contradictions and unverified claims.
- Test on two or three real tasks. After each, ask what guidance was followed, what had to be explained by hand and where instructions contradict. Apply the fixes and test again.