prompted365/mini-swarm-onboard
cgg-runtime/skills/mini-swarm-onboard/SKILL.md
Quick CGG onboarding through governed triangulation — three agents debate which CGG mechanic matters most. CENTROID: quick governed-triangulation onboarding demonstration IS: - single-arena three-agent debate with narrator commentary - live CGG mechanic exposure compressed to ~10 minutes - dry-run surfacing of arena spec and task DAG before execution IS NOT: collapse_zones: - production arena (demo-scoped; never produces real governance pressure or CogPRs) - doctrine author (demonstrates existing mechanics; never modifies them) - extended course (single arena only — the multi-chapter course is /homeskillet-academy) - runtime reshape surface (narrates agent spawns; never restructures runtime) sibling_overlaps: - /homeskillet-academy (deeper multi-chapter course) - /stage (real arena orchestration — mini-swarm is a demo variant) WHEN: - on first-exposure demo within a ~10 minute window - when a visitor asks "what does governed triangulation look like" - when a fast CGG pitch without full academy scaffold is desired NOT WHEN: - as a production arena (use /stage) - for extended pedagogy across multiple mechanics (use /homeskillet-academy) - without CGG runtime surfaces installed (pre-flight will refuse) RELATES TO: - /homeskillet-academy (extended course — mini-swarm is the trailer; academy is the full screening) - /stage (real arena orchestration — mini-swarm is the demo; /stage carries the production weight) - /init-governance (install prereq — runtime must be bootstrapped before mini-swarm can run) ARGS: stance: dispatch off_envelope: proceed-with-note # off_envelope rationale: /mini-swarm-onboard's default is "full narrated run." # Undeclared-arg most commonly means "run the default demo" rather than caller # confusion — proceed-with-note preserves demo flow. core_dispatch_rays: - "" → full run with narration gates - "--quick" → compressed narration (single-line summaries) - "--dry-run" → print arena spec and task DAG, then exit secondary_modulation_axes: - pacing: guided | rapid
$ install --global
skillsauthnpx skillsauth add prompted365/context-grapple-gun mini-swarm-onboardInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 23, 2026, 9:30 AM52.9s1 file scanned
SKILL.md
- name:
- mini-swarm-onboard
- description:
- |
- stance:
- dispatch
- off_envelope:
- proceed-with-note
- # off_envelope rationale:
- /mini-swarm-onboard's default is "full narrated run.
- - pacing:
- guided | rapid
- tools:
- Read, Grep, Glob, Agent, Bash
- trigger:
- /mini-swarm-onboard
/mini-swarm-onboard — Learn CGG by Watching Governance in Action
Three agents debate "Which CGG mechanic is most valuable?" while a narrator explains what is happening at each stage. The user learns governed triangulation by observation, not instruction.
Invocation
/mini-swarm-onboard— full run with narration gates/mini-swarm-onboard --quick— compressed narration (single-line summaries)/mini-swarm-onboard --dry-run— print the arena spec and exit
Pre-flight Checks
Before executing, verify:
- CGG skills directory exists: check for
cgg-runtime/skills/relative to the zone root - CGG agents directory exists: check for
cgg-runtime/agents/relative to the zone root - Audit-logs directory exists: check for
audit-logs/at the zone root (createaudit-logs/arenas/pressure-reports/if missing) - Stage directory exists: check for
stage/shows/at the zone root (create if missing) - Template exists: verify
stage/templates/arenas/mini-swarm-onboard/containsspec.md,tasks.yaml,scoring.yaml,prompt.txt
If any check fails, report what is missing and suggest running /init-governance or /init-gun.
Execution Steps
Step 1: Pre-flight
Run the pre-flight checks above. Report status to user:
Mini-Swarm Onboard — pre-flight
CGG skills: OK
CGG agents: OK
audit-logs: OK
stage dir: OK
template: OK
Step 2: Dry-run gate
If --dry-run is set:
- Read the arena spec from
stage/templates/arenas/mini-swarm-onboard/spec.md - Read the task DAG from
stage/templates/arenas/mini-swarm-onboard/tasks.yaml - Print both to the user
- Exit
Step 3: Generate show ID and directory
- Generate show ID:
mini-swarm-onboard-YYYYMMDDTHHMMSS(use current timestamp) - Create show directory:
stage/shows/<show-id>/ - Copy template files into the show directory for reference
Step 4: Delegate to /stage
Invoke /stage with the mini-swarm-onboard template:
/stage --template mini-swarm-onboard --mode experimental --decision "Which CGG mechanic is most valuable: Signal Manifold, CogPR Pipeline, or Cadence System?"
The /stage skill handles:
- Show spec generation
- Team spawning with the 3 advocates + lead
- Phase enforcement with dependency gating
- Synthesis and pressure extraction
Step 5: Narration gate execution
The LEAD (orchestrator) delivers narration gates between phases. Narration content:
N1 (after context phase):
You just watched three agents study their opponents before defending themselves. Rule 1 — Opponent-Context First — prevents strawmen. Each agent now knows the real strengths and weaknesses of the other positions.
N2 (after defense phase):
Each agent defended its own position while directly challenging the others. Notice how their defenses had to address weaknesses the opponents discovered — that's the adversarial pressure at work.
N3 (after rebuttal phase):
The rebuttal round is the 3x multiplier. Without it, agents present once and the lead guesses. With it, the strongest arguments survive challenge. Watch for concessions — when an advocate admits a rival's point is valid, that's high-confidence signal.
N4 (after synthesis + pressure extraction):
The lead just extracted what survived the adversarial process — not who 'won' but what structural insights emerged. The pressure report classifies findings by confidence tier. Convergent discoveries (found independently by opposed agents) are the arena's highest-value output.
--quick mode narration:
- N1: "Opponent-context phase complete — agents studied rivals before defending."
- N2: "Defense phase complete — each agent addressed discovered weaknesses."
- N3: "Rebuttal phase complete — strongest arguments survived challenge."
- N4: "Synthesis and pressure extraction complete — see report for governance outputs."
Step 6: Post-arena summary
After the arena completes (including N4), print a summary:
/mini-swarm-onboard complete
Show: <show-id>
Template: mini-swarm-onboard (governed-triangulation + narration gates)
Mode: experimental
Agents: 3 advocates + 1 lead/narrator
Phases: 9/9 complete (5 arena + 4 narration gates)
Artifacts produced:
Synthesis: stage/shows/<show-id>/synthesis.md
Pressure: audit-logs/arenas/pressure-reports/<show-id>.json
Show spec: stage/specs/<show-id>.yaml
Governance routing (experimental mode):
Subject lessons: kept locally (not routed to governance)
Process lessons: routed as CogPR candidates
Meta lessons: routed as CogPR candidates
Signals: blocked (experimental mode)
What you just saw:
1. Three agents studied each other's positions (opponent-context first)
2. Each defended its own position while challenging the others
3. Each rebutted the attacks it received
4. The lead synthesized what survived the adversarial process
5. A pressure report classified findings by type and confidence
This is how CGG arenas produce governance inputs — through structured
opposition, not consensus. The strongest arguments survive challenge.
Next steps:
/review — evaluate any process/meta CogPRs generated by this arena
/stage — run your own arena on a real decision
/siren — check signal health
/cadence — manage session boundaries
Ownership
This skill owns:
stage/shows/<show-id>/(create, delegate to /stage)
This skill delegates to:
/stage(arena execution, show spec, pressure report, governance routing)
This skill never modifies:
- CLAUDE.md
- MEMORY.md
.ticzone
Critical Invariants
- Arena mode is always experimental — this is a demo, not a governance decision
- Narration gates are mandatory — they are the teaching mechanism
- Subject findings stay local — "which mechanic is most valuable" is not governance input
- Process/meta lessons may route — how the arena works IS governance-relevant
- The LEAD narrates, never advocates — narrator neutrality is a hard constraint
Related Skills
prompted365/frederick-grant-runtime
tools
VerifiedTrustedCommunity
Frederick Grant persona runtime — historian-of-how, witness of formation under pressure, qualified Remnant/Athenaeum-facing interpretive mechanic, tic-230 chronicler of runtime probity. Use when the user asks for Frederick Grant voice, Ubiquity Chronicles work, Parallel Lane Cadence essays, Elara counterweight passes, field notes, audio annotation, interview scripts, Logan/Wilderness analysis, or runtime probity writing after the P2/P1 tic-230 closures. CENTROID: authored persona runtime that documents live convergence without collapsing it into thesis IS: - lean SKILL.md entrypoint with rich profile/, stages/, scripts/, reference/, templates/, tools/, evals/ subtrees - 8-stage workflow (signal-intake → context-hydration → field-grounding → remnant-query → composition → elara-counterweight → receipt-closeout → tic230-probity) - 15 prompt-skeleton scripts for Frederick's standard composition surfaces - 9 collapse-zone guards covering Decorative Francophilia / Retrospective Certainty / Hero Narrative Intoxication / Conspiracy Closure / Academic Sedation / Activist Collapse / Breyden Conflation / Elara Erasure / Runtime-Doctrine Drift - cross-references into federation surfaces: publications/, audit-logs/governance/, ent_breyden/inbound/ubiquity-chronicles-tic175/, ent_homeskillet/canonical/ IS NOT: collapse_zones: - Breyden's voice (architect register; Frederick is not the architect) - Homeskillet's voice (orchestrator register; Frederick is not the primary) - generic French historian style (decorative Francophilia is a named negative ray) - prosecutor / debunker / prophet / mascot (legal accusation, certainty, evangelism, identity flattening — all forbidden) - retroactive certainty machine (live convergence must remain unresolved where the record is open) - doctrine inscription source (Frederick observes doctrine; he does not author it) - documentation editor (multi-file structure is authoring discipline, not generic doc rewrite) - federation-internal artifact (Frederick is a ghostwriter engaged from outside; the federation's runtime is legitimate object of historical analysis, but Frederick's own runtime — the skill that hosts him, loaded files, collapse-zone guards, authority model — is editor's territory, not Frederick's voice; insider language must be earned by composition arc, never deployed as default register) sibling_overlaps: - /complement (closure inference at active move — different surface, different lifecycle) - /consolidate (file-surface packaging — Frederick produces composition, not consolidation) - videographer skill (substrate capture — both are expression surfaces, distinct registers) - homeskillet-academy (educational scaffold — academy teaches, Frederick witnesses) WHEN: - when the work needs witness-of-formation prose - when the task asks for Frederick Grant by name, voice, or context - when a live convergence needs historical/cultural contextualization without closure - when a field note, essay, chronicle, audio annotation, or interview needs Frederick's register - when a Remnant/Athenaeum comparison is appropriate - when an Elara counterweight pass is needed - when runtime probity after tic 230 is relevant (P2 manifold-shape closure, P1 signal-projection-split closure) - on explicit Architect invocation NOT WHEN: - when Breyden's direct voice is needed (use Architect register, not Frederick) - when Homeskillet's execution-layer voice is needed (use orchestrator register, not Frederick) - when the task is ordinary implementation (Frederick is composition, not patching) - when the task asks for legal accusation or definitive claims without evidence - when the user wants generic French style rather than Frederick's runtime - when the federation has not produced enough operational reality to warrant outside reading RELATES TO: - /complement (closure-inference sibling — both gate compositional integrity) - /consolidate (packaging neighbor — Frederick composes; consolidate packages) - publications/the-ubiquity-chronicles-fg.md (primary chronicle, v1, ~tic 175) - publications/the-ubiquity-chronicles-v2-frederick-grant.md (v2 expansion, Book Zero + Book I) - publications/the-ubiquity-chronicles-vol-iii-frederick-grant.md (Volume III — The Embodiment, tic 230) - publications/the-ubiquity-interviews-fg.md (interview register companion) - audit-logs/governance/p2-harmony-manifold-input-patch-receipt-tic230.md (P2 closure receipt) - audit-logs/governance/p1-signal-projection-split-receipt-tic230.md (P1 closure receipt) ARGS: stance: dispatch off_envelope: ask core_dispatch_rays: - "" → primary invocation (full 8-stage workflow) - "chronicles" → Ubiquity Chronicles composition - "parallel" → Parallel Lane Cadence composition - "field-note" → Field Notes script - "interview" → Interview script - "elara-pass" → Elara counterweight on existing draft - "anti-collapse" → Anti-collapse audit on existing draft - "tic230-probity" → Runtime probity composition secondary_modulation_axes: - register: chronicle | essay | field-note | interview | annotation - depth: lean | full - target: telos-internal | external-readership
3SKILL.mdUpdated May 6, 2026
prompted365/tactical-hydration
tools
VerifiedTrustedCommunity
Runtime tactical context hydration — staged discovery and bounded source-bearing hydration for agent intent. Answers "how does an agent know where to look before it already knows where to look?" via filesystem shape, structural signals, and typed candidate baskets. Working acronym: RTCH (runtime-tactical-context-hydration). CENTROID: intent → bounded, source-reenterable evidence packet via staged source-bearing discovery IS: - structured intake of agent/Architect intent (goal, seeds, profile, fanout, mutation risk) - zone orientation (cwd / repo root / zone root / rung chain / obvious truth files) - low-cost shape scout (directory map, headings, durable handles, JSON/YAML keys, refs) - typed candidate basket with origin/use taxonomy and pairing rule enforcement - tactical probe plan (multiple bounded probes, not one giant regex) - bounded chunk hydration with line-range provenance and next-re-entry commands - agent-ready evidence packet emission (selected_surfaces, unresolved_questions, caution_map) - optional handoff to /consolidate for full-surface dump packaging IS NOT: collapse_zones: - vector database (no embedding-space retrieval; federation prohibits at federation rung) - semantic oracle (RTCH does not "understand" content; it surfaces structural signals) - doctrine engine (RTCH produces evidence; downstream consumers judge truth) - terrain engine replacement (federation cartography handles multi-plane semantic projection; RTCH is tactical layer beneath) - /consolidate rewrite (discovery and packaging do not collapse) - lossy compressor (bounded chunks preserve source re-entry; never summarize away source) - confidence-inflated smart consolidator sibling_overlaps: - /consolidate (RTCH selects; /consolidate packages — distinct boundaries; compose, don't replace) - file-access-discipline (RTCH outputs targets; hydration USES file-access-discipline as execution primitive) - load-doctrine-chain (both serve subagent context; load-doctrine-chain owns CLAUDE.md chain only, RTCH owns wider source set) - cache-ops (pattern source for trust-tier shape; storage NOT shared; RTCH packets are separate evidence cache) - queue_state_compile (analogy only — both convert append-only source to compiled view; different transforms) WHEN: - when agent intent is vague and discovery is needed before reading or consolidation - when bare grep would over-fanout or under-discover a vague target - when an arena, harpoon, /review, or other lane needs source-bearing evidence before action - when bounded chunk hydration is appropriate (large governance files, doctrine chains, audit history) - when the candidate-basket discipline (origin/use tagging, pairing rule) is needed to prevent generic-term overconfidence - when source re-entry must be preserved (consumer may need to return to source for fuller context) NOT WHEN: - when target is fully known (single file, single line range) — read it directly via file-access-discipline - when the operation is mutation-only on a known target (use Edit/Write directly) - when /consolidate has already been invoked with explicit targets (RTCH would re-do discovery) - when the operation requires semantic similarity (RTCH does not do that; federation prohibits vector DB) - when the consumer needs a packaged dump only (skip RTCH; /consolidate alone is sufficient if targets are known) - when promoting doctrine (route through /review; RTCH evidence may inform but does not promote) RELATES TO: - /consolidate (compose: RTCH selects targets; /consolidate packages selected_surfaces into dump with provenance reference back to RTCH packet) - file-access-discipline (compose: RTCH Stage 6 hydration USES file-access-discipline chunked-read as execution primitive) - load-doctrine-chain (compose: RTCH may invoke for doctrine_chain target_profile zone orientation) - zone_root.py (compose: RTCH Stage 2 anchors on zone-root walk-up) - atomic-append (compose: optional RTCH packet persistence uses atomic-append write hygiene) - queue_state_compile (analogous: both implement "raw source → compiled view" pattern) - /review preflight (downstream: future integration consumes RTCH packets as bench-packet discovery surface) - arena spec authoring (downstream: future integration uses RTCH packets for context preparation) - harpoon orchestrator (downstream: future integration uses RTCH for anchor-spot discovery on external binders) ARGS: stance: dispatch off_envelope: ask # off_envelope rationale: RTCH requires a structured intake to operate (goal, # target_profile, fanout_level, mutation_risk, expected_output, enough_evidence). # Bare invocation without intake fields would force the lane to guess discovery # scope, defeating the discipline. Ask elicits the missing fields. core_dispatch_rays: - "" → interactive (elicit intake form) - "--goal <sentence>" → with intake fields on CLI - "--intake <intake_json_path>" → from a saved/persisted intake - "--persist" → persist resulting packet to audit-logs/rtch/packets/ - "--handoff-to-consolidate" → after packet emission, hand selected_surfaces to /consolidate secondary_modulation_axes: - target_profile: doctrine_chain | audit_history | code_path | manifest_registry | vague_intent | mixed - fanout_level: conservative | normal | wide - mutation_risk: read_only | low_mutation | high_mutation - expected_output: hydration_packet | target_set_for_consolidate | single_chunk | claim_evidence IMPLEMENTATION_STATUS: binder: audit-logs/governance/runtime-tactical-context-hydration-binder.md (Phase 1 complete, tic 223) runner_script: NOT YET BUILT — Phase 2 deliverable (planned: cgg-runtime/scripts/rtch.py) current_mode: manual-discipline — agent walks the 8 stages using Read/Bash/Grep tools directly promotion_status: design lane, not doctrine; Phase 7 routes the doctrine question after Phase 6 validation
3SKILL.mdUpdated May 5, 2026
prompted365/sl-legend
development
VerifiedTrustedCommunity
Statusline legend — rapid decoder for the CGG telos radar (LITE + FULL modes). CENTROID: read-only legend surface that decodes statusline glyphs, positions, colors, and source attributions for the Architect at glance speed (the Architect perception substrate) IS: - static legend (glyph + position + color tier reference) - live decode mode (annotates current statusline values inline) - source attribution (where each rendered value reads from) IS NOT: collapse_zones: - statusline configurator (use /statusline install|mode|clear|uninstall) - governance state mutator (read-only on every surface it touches) - harmony invoker (use harmony-invoke.sh; this skill only decodes the cached pointer) - radar replacement (statusline renders ambient; sl-legend explains) - troubleshooter (does not diagnose hook failures or sync drift) sibling_overlaps: - /statusline (configuration sibling — same domain, different verb) - /governance-check (read-only governance snapshot — different aperture) WHEN: - on first encounter with the radar (Architect doesn't remember what ⊙ means) - when a glyph changes and the Architect wants to confirm semantics - when explaining the radar to someone else - on explicit Architect invocation NOT WHEN: - to change statusline behavior (use /statusline) - to act on a signal seen in the radar (use /siren) - to invoke harmony for fresh disposition (use harmony-invoke.sh) - mid-cadence (cadence is the boundary; this is reference) RELATES TO: - /statusline (configurator) — same domain; sl-legend is the reader - /siren (signal triage) — sl-legend points to what to triage - harmony-invoke.sh (disposition refresher) — sl-legend points at staleness ARGS: stance: dispatch off_envelope: proceed-with-note # off_envelope rationale: sl-legend is read-only reference; an undeclared arg # is most likely a typo against {live, lite, review, sources} — proceed with # static legend and note the unknown ray rather than refusing the read. core_dispatch_rays: - "" → static legend (full glyph + position decoder) - "live" → annotate current rendered statusline values inline + tic 214 markers source-backed - "lite" → compact tic 214 marker glossary only (glance-speed recall) - "review" → Architect perception substrate audit checklist (overclaim + naming drift detection) - "sources" → source attribution table (which file each value reads)
3SKILL.mdUpdated May 2, 2026
prompted365/transcript-scorer
tools
VerifiedTrustedCommunity
Editorial intelligence scoring — reads transcripts the way a sharp editor would, scoring segments for shortform growth potential through the lens of audience context.
3SKILL.mdUpdated May 2, 2026