agentleFS
Sign inStart free
aidvggaidvgg/operator-os/.claude/skills/run-coding-session/SKILL.md

run-coding-session

Skill4 starsChanged 11 days agoMITView on GitHub

Run coding work in another repository or initialize a greenfield software project. Baseline existing repos before questions, adapt the harness, freeze task contracts, and require executable gates plus fresh-context evaluation.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Read CLAUDE.md before executing.

    line 13
  2. Very specific:

    Do not edit this file directly.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
<!-- GENERATED by scripts/sync-agent-adapters from ai/AGENT_ROUTES.json. DO NOT EDIT. -->

run-coding-session skill adapter

Canonical skill: skills/run-coding-session/SKILL.md. Read that file in full before acting, then follow it exactly.

This adapter exists so a runtime that discovers repository skills under .agents/skills/ or .claude/skills/ can reach a skill whose canonical copy lives in skills/. It owns no procedure. Do not restate, shorten, or improvise the canonical steps, and do not treat this summary as the skill.

Read CLAUDE.md before executing. It is the shared operating contract and it outranks this skill on precedence, voice, pricing policy, and what counts as a sanctioned write. The canonical skill wins on execution mechanics.

First-party skill of this operating system. Its verification gates are mandatory, never skippable for work that looks quick, and a clean gate is not send authority: nothing client-facing leaves without the operator's explicit go on that specific artifact.

Maintenance

Do not edit this file directly. Change skills/run-coding-session/SKILL.md for procedure or ai/AGENT_ROUTES.json for routing, then run scripts/sync-agent-adapters --write. scripts/repo-doctor blocks stale generated surfaces.

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