agentsclimarketplace

Agent skill creator

Skill Solonnikov/agent-skills/skills/agent-skill-creator

Public collection of agent skills — reusable capabilities, prompts, and workflows for Claude Code and other agentic coding tools.

Install
npx -y skills add Solonnikov/agent-skills --skill agent-skill-creator

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.
  • 2 stars2 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.

What its author says it does

Copied from the file, not written here

Authors new skills for the agent-skills repo with consistent format — tight SKILL.md, frontmatter, references for depth, and a pre-merge checklist. Use when adding a new skill to github.com/Solonnikov/agent-skills, standardizing an existing skill, or auditing a skill's structure.

SKILL.md

2.6 KB, as published. Nobody here has run it

Agent Skill Creator

Meta-skill for writing new skills in this repository. Enforces the format so every skill in the repo stays discoverable, lean, and useful.

When to use

  • Adding a new skill to skills/.
  • Reviewing a PR that adds or modifies a skill.
  • Refactoring an existing skill that has drifted from the format (too long, no references, missing frontmatter).

Authoring workflow

  1. Pick a tight scope. One skill = one job. If the description has "and" in it twice, split it.
  2. Choose a kebab-case name. Matches the folder name. Short, specific — wagmi-contract-interaction, not ethereum-stuff.
  3. Create the folder under skills/<skill-name>/ with a references/ subfolder.
  4. Write the SKILL.md frontmatter (see frontmatter rules).
  5. Draft a tight SKILL.md — operational, not encyclopedic. Sections: short intro, When to use, Authoring workflow (or equivalent), Non-negotiable rules, References.
  6. Move depth to references. Long templates, cheatsheets, checklists, step-by-step guides — all go in references/*.md, linked from SKILL.md by description.
  7. Run the quality checklist before the PR.

Non-negotiable rules

  • Every skill has YAML frontmatter with name (kebab-case, matches folder) and description following the pattern <what it does>. Use when <trigger>.
  • SKILL.md stays short enough for an agent to load cheaply — aim for under 80 lines.
  • Depth goes in references/. Do not duplicate content between SKILL.md and a reference.
  • Reference links in SKILL.md are described by what they contain, not by filename — e.g. [Quality checklist](./references/quality-checklist.md) — pre-merge review against the non-negotiables.
  • Code examples in references use realistic placeholders (<Feature>, <Token>), not real addresses, secrets, or project-specific names.
  • No emojis, no decorative headers, no "Note:" boxes — prefer plain prose.

References

  • Frontmatter rules — required fields and pattern for the description line.
  • File layout — folder structure, how references are organized, what belongs where.
  • Quality checklist — pre-merge review against the non-negotiables.

Keep looking

Skills are one crate of 328,083. 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.