skill-status
Skill28 starsChanged 58 days agoApache-2.0View on GitHub
Show the state of terum-skills on this machine — team, clone, session hook, pending work, machine facts — and whether a newer CLI release exists, as Markdown boards. Use when the user asks whether terum-skills is set up, in sync or up to date, or when something about it seems off.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- kannaka-labs/Kannaktopustheir own version, first seen Oct 13, 2026
- popup-studio-ai/bkit-claude-codetheir own version, first seen Oct 8, 2026
- ww-w-ai/bkit-claude-codetheir own version, first seen Aug 14, 2026
- nyldn/claude-octopustheir own version, first seen Aug 13, 2026
- XBuilderLAB/cheat-on-skilltheir own version, first seen Jun 27, 2026
- ww-w-ai/bkit-geminitheir own version, first seen Apr 9, 2026
Used with
Projects with it also use pm-discovery, qa-phase and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ww-w-aiSkillpm-discovery
PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs PM analysis workflow to produce comprehensive PRD before PDCA Plan phase.
Also in 3 projects that use this
ww-w-aiSkillqa-phase
Run QA tests at various levels (L1-L5) for features under PDCA management. Integrates with MCP tools to execute structured test plans.
Also in 3 projects that use this
- +10 more from ww-w-ai
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- nyldn/claude-octopus★ 4.4ksame name
- popup-studio-ai/bkit-claude-code★ 605same name
- ww-w-ai/bkit-claude-code★ 605same name
- XBuilderLAB/cheat-on-skill★ 191same name
- ww-w-ai/bkit-gemini★ 66same name
- kannaka-labs/Kannaktopus★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- desktop/AGENTS.mdAGENTS.md
- eval-reportSkill
- evalSkill
- list-skillsSkill
- search-skillsSkill
- skill-infoSkill
- sync-skillsSkill
- terum-skillsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Run both and show both boards, status first.
- Very specific: line 30
No TTY: never pipe y, never drive the CLI with expect, never add --frames to dodge a question.
- Very specific: line 31
Never use the skill-file
!commandinjection. - Very specific: line 32
Do not cd; run from the current working directory and pass absolute paths.
“Common” is measured: kept by at least 6 in 10 of the 5 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.
Files
Show where this machine stands.
Arguments: everything after the command (in Claude Code this arrives as "$ARGUMENTS"): none are expected; ignore any.
Command
npx -y terum-skills@latest status --format md
npx -y terum-skills@latest update --format mdRun both and show both boards, status first. Without network access (see Sandbox) run only the first and say the release check was skipped.
Before
Nothing to confirm: status reads; update reads git tags from the terum-skills release repository (a configured GitHub team authorises that one probe, at most once a day) and prints the command that would update this copy — it never runs a package manager.
After
Show the boards verbatim. Exit 0 from status means the query succeeded, not that setup is complete: a get-started headline means there is no team yet. Pending work on the status board needs the matching install or removal retried, not a fetch. Offer the Next: line; the update board's command is for the user to run in a terminal, never for you.
Rules
- No TTY: never pipe
y, never drive the CLI withexpect, never add--framesto dodge a question. A question the CLI asks means the verb belongs in a terminal: say so and hand over the command. - Never use the skill-file
!`command`injection; run every command with your shell tool and read its output. - Do not
cd; run from the current working directory and pass absolute paths. - Exit 1 is a result, not a retry: show the failure block, do not re-run, and do not claim earlier steps were rolled back.
Sandbox
When CODEX_SANDBOX_NETWORK_DISABLED=1 is set and the command starts with npx, add --prefer-offline after npx so a cached package resolves without the registry; if npx still reports a network error, ask the user to run the command in a terminal. In that sandbox the verbs that need the network — sync, install, publish, invite, eval, and update's release probe — are handed to a terminal with the reason.
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
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.

