agentleFS
Sign inStart free
vpeetla-aivpeetla-ai/reflection-agent-pattern/.cursor/skills/setup-vpeetla-skills/SKILL.md

setup-vpeetla-skills

Skill2 starsChanged 5 months agoMITView on GitHub

Bootstrap a vpeetla-ai repo for org skills: issue tracker, triage labels, docs paths, and CONTEXT.md placement. Use when onboarding a new repo, first clone, or when the user says setup skills or configure agent workflow.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run once per repository.

    line 11
  2. Distinctive:

    Add AGENTS.md (Codex) — merge, do not overwrite custom sections

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Setup vpeetla-ai Skills

Run once per repository.

Checklist

  1. Confirm repo is in vpeetla-ai org
  2. Install skills: ./scripts/install.sh --cursor --project . from vpeetla-ai-skills
  3. Copy CONTEXT.md if missing (or symlink from skills repo)
  4. Add AGENTS.md (Codex) — merge, do not overwrite custom sections
  5. Identify stack layer (see governed-ai-stack skill)

Ask the user

  • Issue tracker: GitHub Issues / Linear / local docs/issues/
  • Triage labels: e.g. agent-task, hitl-required, loopforge
  • Docs path: docs/ (default) or adr/

Write .vpeetla-skills.json in repo root

{
  "issue_tracker": "github",
  "docs_path": "docs",
  "stack_layer": "self-improvement",
  "gateway_required": false
}

Verify

  • pytest -q or npm test passes (if applicable)
  • README has honest implementation status table
  • docs/ECOSYSTEM.md or link to ai-architecture-portfolio exists for platform repos

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.

Check your setup, free