agentleFS
rmarjirmarji/chiron-council/skills/log/SKILL.md

log

Skill1 starsChanged 22 days agoMITView on GitHub

Read a Chiron seat's consult log and surface decisions that were never closed. Use when the user asks what a seat told them before, wants open loops, or wants a past decision recorded.

18 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

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 0

    Distinctive

    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:

    Do not read or write a log.md inside a seat directory or inside the plugin root.

    line 14

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

Read a seat's log

ChatGPT and Codex have no /chiron slash commands. This skill is that log flow.

The plugin root is the directory that contains skills/ and scripts/. Follow commands/log.md there, exactly. Wherever that file says ${CLAUDE_PLUGIN_ROOT}, use the plugin root. Run each python3 invocation as its own command. Do not wrap it in a shell substitution or chain it with ;.

Resolve the file with python3 <plugin-root>/scripts/memory.py log <id> --read. That is ~/.chiron/logs/<id>/log.md unless CHIRON_HOME is set. If the printed path does not exist, say "No log file is at that path yet." Do not claim the user never consulted the seat. If --read prints a path under ~/.claude, read it and do not write it. Never write under ~/.claude. A path under ~/.claude is legacy and read-only.

Do not read or write a log.md inside a seat directory or inside the plugin root. The plugin cache is replaced on update. Seat text stays in skills/<id>/SKILL.md; do not copy it here.

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.