agentleFS
Sign inStart free
loganware05loganware05/captains-compass-cursor/.cursor/skills/execution-telemetry/SKILL.md

execution-telemetry

Skill2 starsChanged 31 days agoMITView on GitHub

Records ExecutionRun and Experience artifacts at workstream close

  • Reads credentials

The file

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

    Verify artifacts under .agent/runs/<run-id>.json and .agent/experience/<experience-id>.json.

    line 36
  2. Distinctive:

    Do not commit product-repo Experience JSON by default (control-repo test fixtures only unless Captain requests otherwise).

    line 39

≈ “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

Execution Telemetry

Use this Skill when

Closing a workstream (/close-workstream), preparing a PR completion report, or when the Captain asks to record learning from a finished plan.

Inputs

  • Plan ID
  • Outcome (success | partial | failed | cancelled)
  • Optional: skills used, issue, branch, PR URL, objective summary

Procedure

  1. Confirm plan status is COMPLETE (or Captain-approved stop).

  2. Record telemetry from the control or product repo root:

    ./scripts/record-execution-run.sh \
  --plan-id <plan-id> \
  --outcome success \
  --objective "<short objective>" \
  --skills "skill-a,skill-b" \
  --issue "<issue-url>" \
  --branch "<branch>" \
  --pr "<pr-url>" \
  --repo-root <repo-root>
  3. Verify artifacts under .agent/runs/<run-id>.json and .agent/experience/<experience-id>.json.
  4. Link the Experience id in the completion report / PR body.
  5. Do not commit product-repo Experience JSON by default (control-repo test fixtures only unless Captain requests otherwise).

Output

Schema-valid ExecutionRun + Experience paths.

Prohibited actions

  • Capturing secrets, .env contents, or private keys in telemetry
  • Auto-tuning matcher weights from Experiences (Level 3 — out of scope)

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