Menu
SkillsMP has collected 65 skills from AlmogBaku/aos. Open a skill to review its source and details.
Showing 40 of 65 collected skills.
The aos capability lifecycle's front door. Use when the user asks to install, update, upgrade, remove, or customize an aos capability, mentions or shares a CAPABILITY.md or a capability directory, asks what capabilities are installed or what aos is, or asks…
Detects when a request has drifted from a one-off task into building something persistent (a new skill, agent, cron, or standing automation) and offers to plan it properly before anything gets built. Use BEFORE creating any cron job, scheduled task, recurring…
Evolves a capability's SHIPPED SOURCE — for everyone, not one user. A small tweak lands directly; a change to what the capability owns or does re-runs a scoped version of the capability-build research/design/approval flow. Use for upstream bug reports and…
Changes how an installed aos capability behaves for THIS user and records it in their MOD.md so it survives every upgrade. Use when the user asks to reschedule, retune, retone or otherwise adjust an installed capability ("make the steward run at 22:00", a…
Imports a use case the user already built in this harness into an aos capability draft: inventories the pieces, splits generic mechanism from personal nuance, and emits a package plus a gap report under personal/, never installing it. Use when the user asks…
Installs an aos capability into this harness: reads its briefing, gates the skill names it would claim, renders it against the user's MOD.md, and materializes agents, symlinks, schedules and context blocks behind a diff gate. Use when the user says "install"…
The aos capability lifecycle's front door. Use when the user asks to install, update, upgrade, remove, or customize an aos capability, mentions or shares a CAPABILITY.md or a capability directory, asks what capabilities are installed or what aos is, or asks…
Runs a capability's onboarding interview — typed questions, batched, secrets to the harness store — and writes the answers to the user's MOD.md overlay. Use when installing a capability that ships ONBOARDING.md, when the user asks to redo, refresh or revisit…
Removes an installed aos capability exactly, walking its lockfile entry backwards — jobs, symlinks, marker blocks, config keys, agents it created, its tool — and leaving the user's MOD.md in place so a re-install returns personalized. Use when the user says…
Reviews a capability as architecture and then as prose — traces its flows and decision points, maps its units against the resources powering them, diagrams it, stress-tests the logic, and checks that every command it documents exists and every artifact it…
Upgrades installed aos capabilities by folding the user's uncaptured hand-edits into their MOD.md and re-applying it to fresh upstream, diff-gated, one reviewable commit per render. Use when the user says "update" or "upgrade" — the whole kit or one…
Detects when a request has drifted from a one-off task into building something persistent (a new skill, agent, cron, or standing automation) and offers to plan it properly before anything gets built. Use BEFORE creating any cron job, scheduled task, recurring…
Evolves a capability's SHIPPED SOURCE — for everyone, not one user. A small tweak lands directly; a change to what the capability owns or does re-runs a scoped version of the capability-build research/design/approval flow. Use for upstream bug reports and…
Changes how an installed aos capability behaves for THIS user and records it in their MOD.md so it survives every upgrade. Use when the user asks to reschedule, retune, retone or otherwise adjust an installed capability ("make the steward run at 22:00", a…
Imports a use case the user already built in this harness into an aos capability draft: inventories the pieces, splits generic mechanism from personal nuance, and emits a package plus a gap report under personal/, never installing it. Use when the user asks…
Installs an aos capability into this harness: reads its briefing, gates the skill names it would claim, renders it against the user's MOD.md, and materializes agents, symlinks, schedules and context blocks behind a diff gate. Use when the user says "install"…
Removes an installed aos capability exactly, walking its lockfile entry backwards — jobs, symlinks, marker blocks, config keys, agents it created, its tool — and leaving the user's MOD.md in place so a re-install returns personalized. Use when the user says…
Reviews a capability as architecture and then as prose — traces its flows and decision points, maps its units against the resources powering them, diagrams it, stress-tests the logic, and checks that every command it documents exists and every artifact it…
Upgrades installed aos capabilities by folding the user's uncaptured hand-edits into their MOD.md and re-applying it to fresh upstream, diff-gated, one reviewable commit per render. Use when the user says "update" or "upgrade" — the whole kit or one…
Registers a knowledge tree the user already has as a base and reports how it diverges, writing nothing into it — and runs `kb migrate` when the tree is on the old layout and the user agrees. Use when the user points at an existing KB, notes repo or Obsidian…
Records a thought, note, link or fact the user fired off, verbatim, into the routed knowledge base in under five seconds. Use when the user says something worth remembering rather than something to act on — an observation, a fact about a person or company, a…
Bulk-imports another knowledge base's content into a base — interactively, in checkpointed batches, leaving the source byte-intact. Use when the user wants to migrate, import or bring in an existing KB, notes repo or Obsidian vault ('import my vault',…
Explains how the user's knowledge bases are laid out and which kb skill handles a given job — the tree, the one queue, expiry, links, base health, maintenance. Use when the user asks how their knowledge base works, what state a base is in, why something was…
Answers a question from what is already stored in the user's knowledge bases, citing the page behind every claim and naming the gaps honestly. Use when asked 'what do I know about X', 'where do things stand with Y', when another capability needs stored user…
Records something the user has said they must do themselves: classifies the commitment as next, waiting, someday or trivial, writes it as an action page in their commitments base, and hands off to wt-schedule when it needs real hours. Use when the user…
Estimates a commitment, links it to its project, and blocks time for it on the user's calendar. Use when the user asks to find time for something — "when can I do this?", "find me two hours for the CFP", "block time for that tomorrow", "I want to work on it…
Maintains an existing commitments backlog: overdue, about to expire, stalled, and repeatedly-rescheduled commitments, and someday items gone cold. Use when the nightly schedule fires or the user asks to review or tidy their backlog ('review my backlog',…
Updates an existing commitment when the user reports progress: completion, a new deadline, a stall, or abandonment. Use when the user says "I did that", "finished X", "still waiting on Y", "push that to next week", "I started it", or "forget it, I'm not doing…
Answers questions about the user's own commitments by querying their commitments base, explains the four statuses (next, waiting, someday, done), routes a request to the right work-tracker skill, and states who may change what without asking. Use when the…
Explains how the user's knowledge bases are laid out and which kb skill handles a given job — the tree, the one queue, expiry, links, base health, maintenance. Use when the user asks how their knowledge base works, what state a base is in, why something was…
Registers a knowledge tree the user already has as a base and reports how it diverges, writing nothing into it — and runs `kb migrate` when the tree is on the old layout and the user agrees. Use when the user points at an existing KB, notes repo or Obsidian…
Records a thought, note, link or fact the user fired off, verbatim, into the routed knowledge base in under five seconds. Use when the user says something worth remembering rather than something to act on — an observation, a fact about a person or company, a…
Bulk-imports another knowledge base's content into a base — interactively, in checkpointed batches, leaving the source byte-intact. Use when the user wants to migrate, import or bring in an existing KB, notes repo or Obsidian vault ('import my vault',…
Creates a new knowledge base: interviews the user for purpose, zones, types and curation, scaffolds the tree, registers it, and wires the maintenance schedules. Use when the user wants a fresh base ('create a work base', 'set me up a knowledge base', 'kb init…
Answers a question from what is already stored in the user's knowledge bases, citing the page behind every claim and naming the gaps honestly. Use when asked 'what do I know about X', 'where do things stand with Y', when another capability needs stored user…
Decides which of the user's knowledge bases a piece of content should be filed in, checking the user's own routing rules first and only then asking a model — and never sending a model's guess into a base other people can read. Use when a skill or capability…
Registers a knowledge tree the user already has as a base and reports how it diverges, writing nothing into it — and runs `kb migrate` when the tree is on the old layout and the user agrees. Use when the user points at an existing KB, notes repo or Obsidian…
Records a thought, note, link or fact the user fired off, verbatim, into the routed knowledge base in under five seconds. Use when the user says something worth remembering rather than something to act on — an observation, a fact about a person or company, a…
Bulk-imports another knowledge base's content into a base — interactively, in checkpointed batches, leaving the source byte-intact. Use when the user wants to migrate, import or bring in an existing KB, notes repo or Obsidian vault ('import my vault',…
Creates a new knowledge base: interviews the user for purpose, zones, types and curation, scaffolds the tree, registers it, and wires the maintenance schedules. Use when the user wants a fresh base ('create a work base', 'set me up a knowledge base', 'kb init…