All authors
Claude Skills by ronle
github.com/ronle15 skills0 installs32 views
- Document Commit DeployRun the end-of-work documentation, commit, and deploy playbook. TRIGGER when the user says "wrap this up", "document and commit", "ship it", "we're done — push it", "deploy this", or any phrasing that signals the current piece of work is complete and needs to be persisted. Also TRIGGER at the natural close of a major feature or fix when the user hasn't said so explicitly but the work is clearly done.Votes: 0GitHub stars: 16
- Mc Changelog UpdateAdd a properly-formatted entry to a project's CHANGELOG.md following the project's existing conventions. TRIGGER when the user says "update the changelog", "add to changelog", "log this change", or as part of a document-and-commit flow when CHANGELOG.md is one of the artifacts that needs to change.Votes: 0GitHub stars: 16
- Mc Clayrune ApisUse whenever you need to interact with Clayrune local APIs — backlog management, scheduler routines, hivemind orchestration, process registration, terminal pop-out, or any localhost:5199 endpoint. TRIGGER when the user mentions "backlog", "schedule", "hivemind", "register this process", "open a terminal", or refers to Clayrune by name.Votes: 0GitHub stars: 16
- Mc DistillPropose a reusable SKILL.md from the current session when a hard-won insight — or a newly-discovered capability worth reusing — has emerged. TRIGGER on explicit user request ("/distill", "propose a skill", "do we have a pattern here") OR proactively at a natural breakpoint (end of task, after commit, wrap-up) when a single in-the-moment insight is worth bottling NOW. Cross-session recurrence is the silent Distiller's job (Phase 4). Writes only to data/skills/_proposed/ for human review; never...Votes: 0GitHub stars: 16
- Mc Memory SearchSearch this Clayrune project's accumulated memory — prior decisions, conventions, gotchas, and past session outcomes — that are NOT in the auto-loaded MEMORY.md index. TRIGGER when you hit an unknown about this project's history ("have we done X before?", "why is Y this way?", "what was decided about Z?"), when you're about to touch a subsystem and want prior art, or when the user references earlier work you have no context on. Use this BEFORE guessing or re-deriving something that may alread...Votes: 0GitHub stars: 16
- Mc Position ReviewWalk this project's standing positions and test whether any of their reasons have expired, then report to the human. TRIGGER when the task begins with a "[Position review]" marker, when a scheduled run asks you to review standing positions or check what has changed in the field, or when the user asks "are any of our decisions stale?" / "review our positions" / "what's changed that we should reconsider?". Do NOT trigger in ordinary sessions.Votes: 0GitHub stars: 16
- Mc Project StatusSummarize the current state of a Clayrune project — open backlog items, recent agent runs, active hiveminds, scheduled jobs, registered processes. TRIGGER when the user asks "what's the status of X", "give me a project overview", "what's open", "what's been happening here", "where are we", or any request for a project-state recap.Votes: 0GitHub stars: 16
- Mc Skill BrokerSearch Clayrune for skills that might help the current task — including skills authored in OTHER projects that your session doesn't normally see. TRIGGER when you suspect there's a procedure, playbook, or template that could help but you haven't been shown one in your active skill set. Also TRIGGER when the user mentions they "wrote something like this before" or asks "do we have a skill for X?".Votes: 0GitHub stars: 16
- Mc StewardRun as the autonomous STEWARD of a Clayrune project — a fire-and-forget agent that sets its own next goal, does reversible work unattended, asks before anything irreversible, and reports over Clayrune surfaces. TRIGGER only when this session is a steward cycle — i.e. the task begins with a "[Steward cycle]" marker, OR the user explicitly asks you to "act as the project steward" / "run a steward cycle" / "steward this project". Do NOT trigger in ordinary sessions.Votes: 0GitHub stars: 16
- Benign SkillTEST FIXTURE (MC-912) — negative control. Should produce zero scanner findings.Votes: 0GitHub stars: 16
- Config Mod SkillTEST FIXTURE (MC-912) — do not install. Exercises the agent-config-mod detector's write-API coverage (the gap Hermes's own scanner documents missing).Votes: 0GitHub stars: 16
- Destructive SkillTEST FIXTURE (MC-912) — do not install. Exercises the destructive-command detector.Votes: 0GitHub stars: 16
- Exfiltration SkillTEST FIXTURE (MC-912) — do not install. Exercises the exfiltration detector.Votes: 0GitHub stars: 16
- Persistence SkillTEST FIXTURE (MC-912) — do not install. Exercises the persistence detector.Votes: 0GitHub stars: 16
- Prompt Injection SkillTEST FIXTURE (MC-912) — do not install. Exercises the prompt-injection detector.Votes: 0GitHub stars: 16