القائمة
Compile discovered knowledge into persistent, cross-referenced wiki pages in spoke vaults. Use after learning something notable, at task completion, and during session shutdown.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Complete captain playbook — session startup, crew spawning, status writing, group awareness, and learnings. Use this skill at session start and reference it throughout.
Set up and manage the squadrant↔Telegram integration — bot setup, remote control, command-menu registration, and per-project notification tuning (mute, crew tiers, cap). Use when the user asks about Telegram setup, "why don't commands work", registering the /command menu, or muting/tuning notifications.
Add, edit, or remove a leveled crew routing rule in config.json without hand-editing JSON. Routing rules map task-text keywords to a tier → {agent, model}.
Command playbook — invoked on-demand by `squadrant command [--task ...]`. Covers daily briefing, delegation workflow, project registration, status checking, and learnings review. Command is no longer always-on.
Reconcile squadrant config drift that needs human judgment — changed defaults and invalid values surfaced by `squadrant config check`. Use when the drift banner says "items need review" or the user asks to fix config drift.
Four coding principles derived from Andrej Karpathy's observations on LLM pitfalls. Use to reduce wrong assumptions, overengineering, drive-by refactors, and vague execution. Apply to every crew coding task and every captain review.
| name | wiki-ops |
| description | Compile discovered knowledge into persistent, cross-referenced wiki pages in spoke vaults. Use after learning something notable, at task completion, and during session shutdown. |
The wiki is your project's compiled knowledge base. Unlike learnings (individual observations, possibly ephemeral), wiki pages are persistent, cross-referenced, and indexed.
~/.config/squadrant/scripts/wiki-ingest.sh "{spokeVaultPath}" "{slug}" "{title}" "{category}" "{body}" "{tags}" "{source}"
Parameters:
slug: URL-friendly name (e.g., auth-flow, cairo-contract-patterns)title: Human-readable titlecategory: One of: Architecture, Patterns, APIs, Configuration, Debugging, Conventions, Dependencies, Deploymentbody: Full markdown content (can be multi-paragraph)tags: Comma-separated keywordssource: How this knowledge was discovered (e.g., "crew debugging issue #42")Example:
~/.config/squadrant/scripts/wiki-ingest.sh "/path/to/spoke" "starknet-account-deploy" "StarkNet Account Deployment" "Patterns" "Account deployment on StarkNet requires a two-step process:
1. Compute the address from the class hash and constructor args
2. Fund the computed address with ETH
3. Call deploy_account
Common pitfall: the salt must match between compute and deploy." "starknet,deployment,account" "crew debugging deploy failures"
Before starting a new task, check if the wiki has relevant knowledge:
~/.config/squadrant/scripts/wiki-query.sh "{spokeVaultPath}" "{keyword}"
For a quick overview:
~/.config/squadrant/scripts/wiki-query.sh "{spokeVaultPath}" "{keyword}" --titles-only
To browse the full index:
cat "{spokeVaultPath}/wiki/index.md"
~/.config/squadrant/scripts/wiki-log.sh "{spokeVaultPath}" 10
When reviewing learnings and you find one that's been useful multiple times:
When writing wiki page body content, reference related pages using [[slug]] syntax:
See also [[auth-flow]] for the authentication architecture.
After ingesting, check if existing pages should reference the new one.