agentleFS
ovargasovargas/virtual-team/skills/skill-authoring/SKILL.md

skill-authoring

Skill14 starsChanged 8 months agoMITView on GitHub

Use when creating or modifying a skill — defines structure, size budget, description format, and review checklist for all skills in the plugin

89 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use cloud-api-recipe-authoring, codebuddy-ide-mcp-upgrade 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.
  • TencentCloudBaseSkill

    cloud-api-recipe-authoring

    Author or revise a cloud-api-operations recipe (config/source/skills/cloud-api-operations/references/recipes/). Encodes why the long tail of control-plane capabilities is deliberately NOT wrapped as MCP/CLI tools, the API-first admission test for whether a capability deserves a recipe, the negative and positive lists, the fixed recipe structure, the writing rules distilled from writing-for-agents, the user-facing copy red lines, and the product regeneration/verification pipeline. Also routes contributors (and their agents) to the contribution flow and the pre-PR self-test protocol in references/contributing.md. Use when adding a recipe, judging whether a scenario belongs in the recipe set, updating the recipes index, re-checking existing recipes against the admission test, or onboarding someone who wants to submit one.

    Also in 3 projects that use this

  • TencentCloudBaseSkill

    codebuddy-ide-mcp-upgrade

    升级 CodeBuddy IDE(genie 扩展)内置的 CloudBase MCP,以及 MCP 发版时同步 IDE 侧白名单。当用户提到「更新 IDE 里的 MCP」「内置 MCP 版本太老」「IDE 集成的 CloudBase 功能不足」「改工具白名单 toolWhiteList」「把新 bundle 打进 CodeBuddy」「白名单漂移」「MCP 发版要同步什么」时使用。覆盖:解包定位内置 bundle 与内嵌配置、重新构建 mcp bundle、生成新的工具白名单与系统提示词、安全注入 IDE 并备份、用 MCP 协议验证工具清单、人工端到端验收、一键回滚。

    Also in 3 projects that use this

  • DIL8654Skill

    api-contract-review

    Review ASP.NET Core Web API contracts for HTTP semantics, versioning, backward compatibility, and response consistency. Use when the user asks to review an API, check endpoints, validate REST behavior, or before releasing contract changes.

    Also in 5 projects that use this

  • zaxbysauceSkill

    pr-review-fix

    Codex adapter for addressing pull request review feedback in opencode-swarm. Use when the user asks to fix PR review comments, requested changes, reviewer findings, CI-review notes, or a pasted review summary with low false-positive tolerance.

    Also in 3 projects that use this

  • albertdobmeyerSkill

    git-workflows

    Advanced git operations beyond add/commit/push. Use when rebasing, bisecting bugs, using worktrees for parallel development, recovering with reflog, managing subtrees/submodules, resolving merge conflicts, cherry-picking across branches, or working with monorepos.

    Also in 3 projects that use this

  • rogue-dev-studioSkill

    frontend-engineering

    Expert frontend application engineering: accessible UI structure, state and data-fetching discipline, form/validation UX, responsive layouts, performance budgets, and integration with API contracts. Use when building or refining SPA/web screens, design-system consumption, client-side routing, or fixing UI reliability (loading, empty, and error states).

    Also in 3 projects that use this

  • +6 more from TencentCloudBase

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 80 edited versions we read keep these.

  • 1

    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. Very specific:

    Never use .claude/skills/...

    line 54
  2. Distinctive:

    Before merging a new or modified skill, verify:

    line 73

“Common” is measured: kept by at least 6 in 10 of the 80 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

Skill Authoring Guide

Size Budget (ADR-001)

SKILL.md files must stay under 100 lines. If content exceeds this, split into reference files in a references/ subdirectory.

  • Reference files use disable-model-invocation: true in frontmatter — they are data, not behavioral prompts
  • SKILL.md is always loaded when the skill is active; reference files are loaded on demand
  • Existing skills exceeding the limit should be refactored when touched, not proactively

Frontmatter

Required fields (enforced by tests/validate-frontmatter.test.ts):

FieldRule
nameMatches directory name, kebab-case
descriptionSee Description Format below

Optional fields:

FieldWhen to use
modelOverride the default model (e.g., model: sonnet for mechanical tasks)
loaded_whenDocument which commands load this skill
disable-model-invocationSet true on reference files — marks them as data-only

Description Format

  • Max 1024 characters
  • Third person, not imperative (the description talks about the skill, not to the user)
  • Must include "Use when [trigger condition]" — this guides the auto-triggering system
  • Describe what the skill enforces or enables, not just what it is

Good: Use when implementing any feature or bugfix, before writing implementation code — enforces red-green-refactor cycle with configurable strictness

Bad: TDD skill for testing (no trigger, no enforcement description)

File Structure

skills/<name>/
  SKILL.md              — Main file (always loaded, under 100 lines)
  references/           — Optional, lazy-loaded sub-topic files
    example.md          — Data tables, examples, checklists
  • Cross-references use root-relative paths: skills/git-practices/SKILL.md
  • Never use .claude/skills/... or relative ../ paths

Progressive Disclosure

SKILL.md contains behavioral rules — the instructions the AI must follow when the skill is active. Keep it focused: conditions, rules, verification steps.

Reference files contain supporting data — comparison tables, example lists, rationalization catalogs, detailed checklists. They are read only when the specific sub-topic is relevant.

This split is how you stay under 100 lines without losing depth. See skills/test-driven-development/ for the model: SKILL.md at 98 lines, with references/test-quality.md and references/rationalizations.md loaded on demand.

Scripts

Scripts are for deterministic operations only: file manipulation, formatting, validation, template generation. Never use scripts for AI judgment calls.

  • Skill-specific scripts go in the skill directory
  • Shared scripts go in scripts/ at the repo root

Review Checklist

Before merging a new or modified skill, verify:

  • SKILL.md is under 100 lines
  • Frontmatter has name and description
  • Description is under 1024 chars, third person, includes "Use when [trigger]"
  • Cross-references use root-relative paths
  • Reference files (if any) have disable-model-invocation: true in frontmatter
  • Content split: behavioral rules in SKILL.md, data/examples in reference files
  • npm test passes (frontmatter validation, file reference validation)

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.