agentleFS
Sign inStart free
Codagent-AICodagent-AI/agent-skills/skills/init/SKILL.md

init

Skill31 starsChanged 6 months agoMITView on GitHub

Initializes Agent Skills in a project by checking prerequisites and verifying the validator configuration. Use when the user says "init", "set up agent-skills", or "initialize agent-skills".

  • Installs packages

We split this skill into the rules it gives an agent

8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 119 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check that the Agent Validator CLI is installed.

    line 18
  2. Very specific:

    If not found: "Agent Validator CLI is required.

    line 21
  3. Very specific:

    If found, extract the version number and verify it is ≥ 0.15.

    line 22
  4. Distinctive:

    Use this shell snippet to compare versions:

    line 24
  5. Very specific:

    If the CLI is missing or out of date, stop.

    line 30
  6. Very specific:

    Stop on missing or outdated prerequisites — tell user what to install/run and resume with /codagent:init

    line 57
  7. Very specific:

    Never overwrite .validator/config.yml — only add/update entry points and reviews

    line 58
  8. Distinctive:

    Use the hosting runtime's native mechanism to locate the plugin's root directory

    line 59

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

Init

Set up Agent Skills in the current project. This skill is idempotent — safe to re-run.

Announce at start: "Initializing Agent Skills in this project."

Steps

1. Check Prerequisites

Check that the Agent Validator CLI is installed. If missing, tell the user what to install and stop.

  • agent-validator — run agent-validator --version.
    • If not found: "Agent Validator CLI is required. Install with npm install -g agent-validator, then run agent-validator init in your project, then re-run /codagent:init."
    • If found, extract the version number and verify it is ≥ 0.15. If too old: "agent-validator 0.15 or higher is required (found <version>). Upgrade with npm install -g agent-validator@latest, then re-run /codagent:init."

Use this shell snippet to compare versions:

version_gte() { [ "$(printf '%s\n' "$2" "$1" | sort -V | head -1)" = "$2" ]; }

Example: version_gte "$installed_version" "0.15" returns true if $installed_version ≥ 0.15.

If the CLI is missing or out of date, stop. The user must resolve it first, then resume /codagent:init.

Validator config (check after CLI passes):

  • .validator/config.yml must exist. If not found: "Validator config not found. Run agent-validator init in your project first, then re-run /codagent:init." Stop.

2. Print Success

Print a summary:

Agent Skills initialized successfully.

Available skills:
- /codagent:propose — evaluate an idea and write a proposal
- /codagent:spec — interview-driven requirement discovery
- /codagent:design — brainstorm architecture and write a design doc
- /codagent:test-plan — plan automated and acceptance testing
- /codagent:plan-tasks — break a change into scoped task files
- /codagent:finalize-pr — push PR, wait for CI, fix failures

3. Commit

Invoke /agent-validator:validator-commit skip to commit any scaffolding changes. Checks are skipped because init only writes boilerplate.

Guardrails

  • Stop on missing or outdated prerequisites — tell user what to install/run and resume with /codagent:init
  • Never overwrite .validator/config.yml — only add/update entry points and reviews
  • Use the hosting runtime's native mechanism to locate the plugin's root directory

Download now (ZIP)

  • Other versions131 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 131

    1. microsoft/vscode★ 194ksame name
    2. mcollina/skills★ 2ksame name
    3. skyllwt/OmegaWiki★ 1.7ksame name
    4. DAIR-AutoResearch/AutoSci★ 1.7ksame name
    5. PKU-DAIR/AutoSci★ 1.7ksame name
    6. skyllwt/AutoSci★ 1.7ksame name
    7. TokenRollAI/cc-plugin★ 483same name
    8. pipecat-ai/gradient-bang★ 420same name
    9. AlexPEClub/ai-coding-starter-kit★ 382same name
    10. dannysmith/tauri-template★ 312same name

    121 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use daily-arxiv, exp-eval 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.
    • LambenthanSkill

      daily-arxiv

      每日从 arXiv 拉取新论文，过滤相关性，auto-ingest 高优先级论文，检测 SOTA 更新

      Also in 5 projects that use this

    • LambenthanSkill

      exp-eval

      实验判决门：Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

      Also in 5 projects that use this

    • skyllwtSkill

      exp-pilot-eval

      Pilot result evaluation — read pilot results, apply success criteria, update idea page (pilot_result, failure_reason if failed), generate PILOT_VERDICT_REPORT. Called by /ideate Phase 5 after /exp-pilot-run.

      Also in 4 projects that use this

    • skyllwtSkill

      exp-pilot-run

      Pilot experiment execution — read Pilot Spec YAML, write pilot code, run experiment(Confirm with the user before operation and require the applicant to conduct manual inspection), return results. Called by /ideate Phase 5. Does NOT modify wiki pages or judge pass/fail.

      Also in 4 projects that use this

    • gaebalaiSkill

      codex-system

      PROACTIVELY consult Codex CLI, your highly capable supporter with exceptional reasoning and task completion abilities. Codex is a trusted expert you should ALWAYS consult BEFORE making decisions on: design choices, implementation approaches, debugging strategies, refactoring plans, or any non-trivial problem. When uncertain, consult Codex. Don't hesitate - Codex provides better analysis. Explicit triggers: "think deeper", "analyze", "second opinion", "consult codex".

      Also in 3 projects that use this

    • +6 more from Lambenthan
    • +1 more from skyllwt
  • In this repository30 other files it gives its agents.

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.

Check your setup, free