agentleFS
calven-aicalven-ai/marketing-as-code/.agents/skills/doctor/SKILL.md

doctor

Skill10 starsChanged 40 days agoMITView on GitHub

Say what is wrong with this checkout in plain words and fix what is safe. Use when asked for the "doctor", "something is red", "the check failed", or when sync or propose report a problem.

  • Reads credentials

85 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use uninstall, cancel and 9 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.
  • AnthropicSkill

    uninstall

    Uninstall a community skill that was installed via the hub. Confirms before deleting files, refuses to touch first-party plugin skills, and logs every action. Use when the user wants to fully remove a community skill ("uninstall [skill]", "remove this skill") rather than just disable it.

    Also in 6 projects that use this

  • woosikkimSkill

    cancel

    Clear any stale OMC-Slim state

    Also in 3 projects that use this

  • ibahgatSkill

    mode

    Inspect or switch omi operating mode/profile for speed, depth, autonomy, or strict quality gates.

    Also in 3 projects that use this

  • BlockSkill

    open

    Open markdown documents in Penpal for collaborative review. Use when you want a human to review a document, plan, or research artifact.

    Also in 3 projects that use this

  • QinghongLinSkill

    editor

    Read analyst.json and detective.json, make all editorial decisions — what the blog argues, which findings matter, narrative arc and section structure. No visual design. Outputs editor.md (prose) and editor.json (structure with edt_xx IDs).

    Also in 3 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 15 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 64 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run python3 scripts/doctor.py --fix (add --github when the GitHub CLI is logged in, to check the repository settings too).

    line 20
  2. Very specific:

    Never read .env or ask for a key value.

    line 36

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

Doctor

The repair word beside the lifecycle. scripts/doctor.py finds the problems; this skill explains them and fixes the ones that need judgment.

Procedure

  1. Run python3 scripts/doctor.py --fix (add --github when the GitHub CLI is logged in, to check the repository settings too).
  2. For each remaining finding, say what it means for the person, then either fix it (a frontmatter value, a broken link, a misplaced file moved with git mv, a naming slip) or name the one action only they can take. A stale review date is theirs: ask the owner whether the content still holds before touching the date.
  3. "Your machine" lines: relay the action as written. When it is a terminal command (gh auth login --web), tell the person to run it in their own terminal or the desktop app's terminal, and what they will see: a code, then the browser.
  4. When clean, say so in one line. If files changed, /propose sends the fixes.

Rules

  • Never read .env or ask for a key value; say where the key lives (docs/secrets.md).
  • Unfilled templates are /setup's job; say so and stop.
  • The check on GitHub runs the same lint, so green here means green there.

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.