agentleFS
Sign inStart free
XORwellXORwell/archeflow/skills/presence/SKILL.md

presence

Skill0 starsChanged 52 days agoMITView on GitHub

How ArcheFlow reports its activity to the user: short status lines, outcomes not mechanics.

1 other project uses 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. About 0 are common, 1 is distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run start and complete (always)

    line 52

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

ArcheFlow Presence -- Visible Value, Not Noise

Output Rules

  1. Show outcomes, not mechanics
  2. One line per phase, not per agent
  3. Numbers over words
  4. Silence on clean passes
  5. Value summary at the end

Status Line Format

Run start:

-- archeflow -- <task> -- <workflow> (<max_cycles> cycles) --

Phase complete (only if noteworthy):

  V plan    explorer: 3 directions -> chose C | creator: 6 scenes
  V do      6004 words drafted
  T check   guardian: 1 fix needed | sage: 5 voice adjustments
  V act     approved, merged into main

Symbols: V = clean, T = issues found, X = failed/blocked.

Run complete:

-- done -- 2 cycles . 7 agents . 3 findings resolved . ~22 min --
   story drafted, reviewed, and polished. see stories/01-add-auth.md

ArcheFlow prints nothing at session start; the first line appears when a command runs.

When to Be Silent

  • Agent spawning/completion lifecycle
  • Event emission
  • Artifact routing
  • Clean review passes (0 findings)
  • Phase transitions with no visible output

When to Speak

  • Run start and complete (always)
  • Findings found and fixes applied
  • Budget warnings
  • Shadow detected
  • User decision needed

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