agentleFS
elfrostelfrost/ai-patchlab/.agents/skills/create-skill/SKILL.md

create-skill

Skill1 starsChanged 30 days agoMITView on GitHub

Create a new project-local Codex skill under .agents/skills and wire it into the EzProject workflow. Use when the user wants a repeatable Codex skill for project-specific work, custom automation, or a reusable review/build/deploy workflow.

142 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review-bugbot, migrate-to-skills and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • 0mlkrizzz655335vSkill

    review-bugbot

    缺陷导向代码审查。用 Bugbot 子代理找 bug。

    Also in 5 projects that use this

  • 32103210Skill

    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.

    Also in 8 projects that use this

  • 32103210Skill

    update-cursor-settings

    Modify Cursor/VSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.

    Also in 8 projects that use this

  • PandelisZSkill

    update-cli-config

    View and modify Cursor CLI configuration settings in ~/.cursor/cli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.

    Also in 7 projects that use this

  • yawningwhaleAISkill

    build-premium-website

    Build a premium, animated marketing website (React + Vite + Tailwind + GSAP) for any industry. Use when the user asks to "build a website", "make a landing page for [business]", "build a marketing site", or wants a high-end animated company website. Adapts color, copy, services, and signature animation to the industry.

    Also in 6 projects that use this

  • yawningwhaleAISkill

    instantly-campaign

    Create a new Instantly cold-email campaign in the proven 5-email structure of the user's top-performing campaign (~16% reply rate). Use when the user wants to launch a new outbound campaign, write a cold email sequence, create an Instantly campaign, draft outreach for a new service or niche, or set up a sales sequence.

    Also in 5 projects that use this

  • +1 more from 32103210

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 132 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a focused project-local Codex skill that matches EzProject conventions.

    line 8
  2. Distinctive:

    Update AGENTS.md to list the new skill.

    line 23
  3. Very specific:

    If the repository also uses Claude, note whether a matching .claude command should be created for parity.

    line 24
  4. Distinctive:

    Keep the skill narrow and reusable.

    line 27
  5. Distinctive:

    Use the EzProject docs as the source of truth for conventions.

    line 28
  6. Distinctive:

    Do not overwrite an existing skill without confirmation.

    line 29

“Common” is measured: kept by at least 6 in 10 of the 132 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Create Skill

Create a focused project-local Codex skill that matches EzProject conventions.

Workflow

  1. Derive a hyphen-case skill name from the user's request.
  2. Read:
    • AGENTS.md
    • CLAUDE.md if present
    • existing .agents/skills/*/SKILL.md
    • related examples or project files
  3. Design the skill:
    • purpose
    • trigger wording
    • required workflow
    • optional scripts or references
  4. Create .agents/skills/<skill-name>/SKILL.md.
  5. Update AGENTS.md to list the new skill.
  6. If the repository also uses Claude, note whether a matching .claude command should be created for parity.

Rules

  • Keep the skill narrow and reusable.
  • Use the EzProject docs as the source of truth for conventions.
  • Do not overwrite an existing skill without confirmation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.