Inspect org-os organizational state — dashboards, projects, instances, plans, decisions — without leaving the agent. Pages render to plain text via npm run page in the operator's org-os repo.
Turn a raw lead (link, paste, transcript, repo, tweet, forum post) into typed Toolkit objects routed to the right layer, with provenance + maturity + public-use state preserved. The framework's flagship intake skill.
Assemble a track/journey for an audience + context — select concepts, surface resources, propose options, run the compatibility engine, emit deployment checks, and produce a draft track (and optional draft deployment).
Structural-integrity review — apply the audience-segmented review prompts, grade an artifact against the three-level model, run the minimum enforceable safeguards, and flag (never certify) overclaiming / visibility-not-falsifiability.
Operate the framework's ingestion pipeline end-to-end — claim work orders, read sources, produce candidate typed objects, and hand them to the CLI accept gate. The batch big sibling of capture-and-route. Agents NEVER write to storage; only the CLI does.
Derive a foreign corpus's implicit ontology and map it onto the semantic kernel — reuse existing types where they fit, propose namespaced extensions with mapstocore where they don't, and emit a crosswalk. How external knowledge bases join without being shoehorned.
Register a knowledge source as a first-class federation peer — create its source-system card (return path, reuse conditions, crediting, currentness), wire the provenance chain, and enforce referencing discipline before any content is ingested from it. Sources are peers, not link pools.
Run a guided human review session over the KB's review queue — inspect raw/AI-assisted objects with the reviewer, promote K1 maturity honestly, never in bulk, never without a named human. The operator of "raw is never auto-promoted".
Suite of tools for creating elaborate, multi-component HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components — not for simple single-file HTML/JSX artifacts. In org-os instances, use for shareable…
Guided vault-safe commit — stage, write a conventional message, commit to your operator trunk (never main), push. Use when the user types /commit or says "commit this", "save my work", "commit and push".
Generate a compact handoff prompt — sync an operator's trunk, point them at a doc/section (or task) to work on, commit to their trunk, PR to main. Use when the user types /handoff or says "hand this to ", "make a handoff prompt".
Vault-safe sync — fetch, fast-forward your operator trunk, report drift vs main. Never stashes. Use when the user types /sync or says "sync", "pull latest", "catch up with the team".
Richard Feynman's first-principles thinking and explanation frameworks. Use when trying to understand a complex system, learning something new, needing to explain a complicated concept simply, or debugging through systematic elimination.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI).…
Assess any org-os instance for identity, lineage, version, machinery, structure and freshness defects, then sync it from the framework — the guided assess → read scorecard → sync → verify flow. Assess is proven across the live fleet; the file-level overlay sync is accepted end to end against a real instance.
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Build, update, and query the org's Graphify knowledge graph; maintain the knowledge-gaps registry for the curator.
★not rated 5 4d agoA27 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: