All authors
Claude Skills by manence
github.com/manence11 skills0 installs1 views
- CheckpointUse it when the user says they are about to wipe the context — "I'm going to clear", "let's close the session" — and on the agent's own initiative when the session has produced a lot and the context is getting heavy. Prepares the handover: every open thread filed in the inbox, log, memory and workstreams brought up to date, everything versioned committed, and pushed where a push publishes nothing, the environment left as found, and a report that says where to pick up; no external action is pl...Votes: 0GitHub stars: 11
- Close WorkUse it when a deliverable is finished and approved, when a workstream is being abandoned, or to regularize a production folder born without an About.md. Closes the workstream — moved under the same name to <domain>/done/, durable facts distilled into the knowledge base, a wrap-up in the log — and is the sole guarantor of durability, since production artifacts are disposable.Votes: 0GitHub stars: 11
- Connect AdapterUse it when plugging something new into a Manence OS core — a neighboring repository, a knowledge bundle, a capability, a confidential adapter — or when an existing connector's declaration needs fixing. Validates the adapter contract, routes by confidentiality (the connector map in the shared AGENTS.md, or the gitignored CLAUDE.local.md for confidential ones), writes the map line, declares the attachment in .claude/mos.json (never for a confidential adapter), and logs it.Votes: 0GitHub stars: 11
- ConsignesUse it at session start when `inbox/` holds `type: instruction` items in `status: deposee` (a session-start signal may flag them), whenever the user asks ("process the instructions"), and before the weekly review. Handles those items dropped off from Manence UI or any front desk (an answer to a wait, a "done", an instruction about a workstream or about one of its documents), records each effect in the About of the workstream concerned, sets the item to `status: traitee`, writes one `event |` ...Votes: 0GitHub stars: 11
- Kb IngestUse it whenever an outside source has to become knowledge — an article, a PDF, a transcript, a web page, raw notes, or something the user simply pastes in. Produces one concept page integrated into the knowledge base following the wiki method: the index and the linked pages brought up to date, contradictions with what is already there flagged.Votes: 0GitHub stars: 11
- Kb LintUse it when the knowledge base calls for an audit rather than an edit: periodically as it grows, before a release or a handover, when the weekly review reports that the KB has moved, or when a contradiction is suspected. Produces a dated report of proposals (contradictions, stale claims, orphans, concepts without a page, missing cross-references, data gaps, pruning); it repairs nothing.Votes: 0GitHub stars: 11
- Open WorkUse it whenever the user wants to work on something new that has an identifiable deliverable — a campaign, a webinar, a document, an exploration. Opens a workstream in the container's production, after checking against the routing table in AGENTS.md that it is one, and leaves a dated folder, its About.md, and a work-open entry in the log. IMPLICIT TRIGGER: creating a work folder in production IS opening a workstream; the discipline applies on its own, even if no one invoked the skill.Votes: 0GitHub stars: 11
- Outward WatchUse it about once a week, ahead of the weekly-review that consumes it — by hand or as a scheduled routine — and whenever the user asks what is moving outside. Looks outward at the substrate (the harnesses the MOS runs on and their vendors, agentic practice; the same for every MOS) and at the trade (a slot each installation fills for itself), puts every finding through a single filter, "what does this change for this MOS, or for the framework?", writes a dated report into the MOS's watch folde...Votes: 0GitHub stars: 11
- Weekly ReviewUse it once a week — by hand or as a scheduled routine — and whenever the user asks "where do we stand?", wants the state of things, or a health check of the system. Puts the core and production through a sieve (lint, inbox, workstreams and their waits, effect measures, routines, freshness of the framework and of the skills, the outward watch, drift) and produces a synthesis with proposed actions, traced in the log. It observes and proposes; it fixes nothing.Votes: 0GitHub stars: 11
- Skill CraftUse it when you write, change, review, or retire a skill in a Manence MOS (`.claude/skills/`): deciding where each sentence lives (against AGENTS.md, the Spec, and the hard boundary), keeping the stops, testing that the description routes on its own, comparing the installed copy with the version the framework ships, and leaving a trace. Not for generic prompt craft, nor for a skill outside a MOS.Votes: 0GitHub stars: 11
- UpgradeUse it when the weekly review reports a newer version of the framework than the core's `.claude/manence-version`, or when the user asks to bring the MOS up to date. Runs `upgrade.sh` as a dry run, gets the user's GO, applies, gives each conflict its fate (dropped, moved into the MOS's own files, rewritten in English for upstreaming, or held for the user when a local override contradicts a framework rule), confirms with `--resolved`, does the manual touches the script lists, and leaves an `eve...Votes: 0GitHub stars: 11