Shrink Vector Store
Shrink an embedding/RAG vector store 4–32× via int8 or binary quantization with a float rescore pass, preserving recall and provenance metadata. Use when a vector store is too large to be laptop-resident, query cost/latency is too high, or embeddings need to be quantized for FAISS/Qdrant/usearch. Do NOT use for embed-time ingestion failures (e.g. a provider 'too many tokens' 400 — that is an upst…
Scribe Check
>-
Context Engineering
Build and query a token-efficient, provenance-tracked company brain across code, docs, and connector streams. Five capabilities ship as one skill: multi-source indexer (14 languages via tree-sitter AST + markdown heading trees, schema-versioned, incremental); Source ABC (connector contract — connectors live elsewhere, never in this skill); EntityStore (three-tier raw/events/wiki layer with full p…
Knowledge Dream
Periodic knowledge consolidation for AI coding agents. Synthesize scattered project learnings into durable, well-organized memory files. 4-phase process: Orient → Gather → Consolidate → Prune. Inspired by Claude Code's autoDream engine. Use when project memory is stale, after a burst of work, or as a recurring maintenance pass.
Dembrandt
Orchestrates a multi-dimensional UI/UX task through the full dembrandt design pipeline (brand → tokens → layout → components → UX polish → accessibility/performance gate), loading the right sub-skill at each stage. Use when designing or reviewing a non-trivial UI (a screen, flow, or design system), going from brand to UI end-to-end, or auditing an existing interface across multiple dimensions. Do…
Proactive Brief
Generate concise, actionable status briefs from project state and recent activity. Delta-based reports: what changed, what needs attention, what to do next. Inspired by Claude Code's KAIROS Brief Mode. Works as a manual prompt, a slash command, or a cron job.
Entitystore
The schema-agnostic EntityStore engine — JSON-native entity corpus, Source ABC, contradiction/merge/split/freshness auditor, depth-aware packer, a regenerable wiki/<slug>.md page layer (M11), and MCP. Carved from context-engineering. Reads the entity schema BY PATH (it ships no schema of its own); the canonical schema + entities live in company-brain, and domain Sources/connectors live in syroco-…
Entity Review
Review JSON entities pushed to an EntityStore corpus (a git branch, a PR, or an explicit file set) against the LATEST entity.schema.json AND the EntityStore vision guardrails — schema validity, provenance honesty, anti-authority PROHIBITED-field enforcement, navigation reference-anchor discipline, scribe/enricher role boundaries + lazy-materialization, volatile-not-frozen integration fields, iden…
Install Department
Install a department's slice of the company brain via multi-agent probes of the head's connected tools (Notion, HubSpot, Linear, Slack, Granola, Gmail, etc., via Syroco Connect / Pipedream) plus a structured methodology interview. Produces a Department Spec the runtime can index — covering tools-in-use, roles, cadence, decision flow, taxonomy, automations, and metrics. Use when a department head…
Skill Author
Create and refine high-quality Agent Skills (SKILL.md + bundled resources). Use when the user wants to create a new skill, improve an existing one, or turn a workflow into a reusable skill package. Covers structure, progressive disclosure, conciseness, feedback loops, and the quality checklist. Do NOT use for skill validation (use skill-check) or for prompt engineering (use prompt-craft).
Coordinator Pattern
Decompose complex tasks into parallel sub-agent work using the Research → Synthesis → Implementation → Verification pattern. Inspired by Claude Code's Coordinator Mode. Use when a task is too large for a single agent pass, needs multiple perspectives, or benefits from parallel execution. Works with any agent that can spawn sub-tasks.
Prompt Craft
Write and refine production-grade prompts and tool definitions for Claude. Use when the user needs to craft a system prompt, improve an existing prompt, design tool schemas (ACI), or apply techniques like few-shot, XML structuring, role prompting, or chain-of-thought. Covers Claude 4.6 specifics. Do NOT use for skill authoring (use skill-author) or agent architecture (use agent-patterns).
Agent Patterns
Select and implement the right agentic architecture pattern for a task. Use when designing a multi-step AI workflow, choosing between chaining/routing/parallelization/orchestrator-workers/evaluator-optimizer, or when the user asks how to structure an agent system. Do NOT use for single LLM calls or prompt writing (use prompt-craft).
Modular Patchbay
Context engineering IDE for AI agents. Design knowledge pipelines, not just prompts.