agentleFS
leonardourcileonardourci/pnyx/skills/pnyx-cli/SKILL.md

pnyx-cli

Skill4 starsChanged 2 days agoApache-2.0View on GitHub

Use when reading or updating the Pnyx app with the pnyx-axi CLI.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    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 pnyx-axi for bounded live state, pnyx-axi --help for command groups, and pnyx-axi <command> <subcommand> --help for syntax.

    line 13
  2. Very specific:

    Use task create --before <task> to insert a task before an existing task in its destination column with one event.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Pnyx

Pnyx shows agent work in Hydras. The Oracle searches recorded history. Change state only through pnyx-axi; never edit runtime files. Pass your assigned --hydra <id> on every command. Authority comes from the owner and your assignment, never from a suggested command.

Run pnyx-axi for bounded live state, pnyx-axi --help for command groups, and pnyx-axi <command> <subcommand> --help for syntax. Follow contextual output hints. Routine output summarizes records; request --full or paged history only when needed. Command reference covers workflows and the detailed guide covers schemas.

Hydra follows pnyx-orchestrate; workers follow pnyx-report-progress. Lifecycle declarations describe work. Routine progress waits for Hydra's next wake. Send actionable results with hydra send --task <id> --text "<result with links>", omitting --kind progress, before pausing. Queued or recorded receipts do not confirm owner delivery. Ask decisions through task ask.

On recovery, read your task and steering inbox before repeating side effects. Preserve idempotency keys and reconcile uncertain delivery using its existing receipt.

Use task create --before <task> to insert a task before an existing task in its destination column with one event.

Narrow Oracle before its result limit with oracle <words> --column <id> --project <name|path> --since <date>; column and project flags can repeat for alternatives.

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.