fakoli-plugins

This skill should be used AFTER code review and verification pass, when the user wants to "ship this", "ship the task", "open and merge the PR", "push, PR, wait for CI, and merge", or otherwise run the mechanical tail of a one-PR-per-task loop. It pushes the current branch, opens a PR, waits for CI to reach a terminal state, merges (squash + delete branch), syncs the base branch, and optionally runs a post-merge command (e.g. `anvil apply`). It makes NO review decisions — the human or agent gates that first.

Mine past coding-agent sessions (Claude Code, Codex, OpenClaw, Cursor CLI) into local-model eval suites executable via anvil-serving. Retro-first — consumes session-retro output dirs and cross-session findings themes, curates candidates into deterministic check-based evals sized for local models, emits anvil-serving-compatible eval-data suites, and runs them against any OpenAI-compatible endpoint. Use when the user asks to "create evals from my sessions", "build local-model evals", "turn this retro into evals", "which work classes can my local model handle", or wants evidence for anvil-serving routing decisions. Reads only local session logs; writes only to the eval-data root the user chooses.

Generate spec-INDEPENDENT breakage probes for a change — attack it along fail-closed, malformed-input, resource-exhaustion, and state-drift axes, not by re-reading its own tests. Use before opening a PR, as anvil execute's verify-left stage, when the user asks to "recall-mode verify", "red-team this change", "what breaks this", "find failure modes", or wants an independent breakage pass that doesn't reuse the implementer's assumptions. Reports findings; does not fix.

Scan source for Windows/cross-platform CLI hazards before shipping — non-ASCII in printed strings (the cp1252 console crash), hardcoded python3, heredoc backslash mangling, Node .cmd/.bat spawns, set -e in hooks. Use when the user asks to "check for encoding issues", "scan for Windows portability", "cli hygiene", is about to ship a CLI/script change, or wants the deterministic form of the ship-loop Windows discipline. Advisory (never blocks); wire it as a gate-router gate.

Route changed file paths to the verify commands this repo requires before shipping — docs changed means docs strict build, shell changed means bash -n, CLI changed means the encoding smoke test. Use before committing/opening a PR, when the user asks "what checks do I need to run", "run the gates", "gate check", or after substantive edits in a repo with a .claude/gate-router.local.md rules file. Deterministic local gates instead of session memory; also helps AUTHOR the rules file for a new repo.

Save or update this project's cross-session handoff note — the resume point for the next session, shared across checkouts of the same git remote and across linked worktrees. Use when the user types /handoff (optionally with a one-line summary), says "save a handoff", "note where we are for next time", "write a handoff before I clear context", or is wrapping up a session.

Show this project's saved cross-session handoff note (the resume point shared across checkouts of the same git remote and across linked worktrees). Use when the user types /recall, asks "where did we leave off?", "what's the handoff?", "what was I working on?", or "catch me up".

Run the full ship loop for a feature or fix — sync and isolate in a worktree, scope with ground-truth sweeps, implement with reality-faithful tests, gate on a multi-angle adversarial review, merge, and close the follow-up loop (promotions ledger, out-of-diff issues). Use when the user says "ship this the usual way", "run the loop", "ship-loop", starts substantive feature/fix work in a fakoli repo, or asks to take a change from idea to merged PR with the standard review gate. The adversarial review is the merge gate — never merge substantive work without it.

Start, stop, or check the anvil-pulse dashboard — a live local web page showing active anvil claims (actor, phase, elapsed, lease countdown), the event feed, and stuck-state detection (healthy / quiet / possibly wedged / lease expired) for long autonomous runs. Use when the user asks to "watch this run", "open the anvil dashboard", "is the agent stuck?", "monitor the claims", "start/stop pulse", or wants a heartbeat view of an anvil project. Also installs an optional Claude Code statusline segment on request. Read-only over anvil state; sends nothing externally.

Review a plugin, skill bundle, or agent workflow that has been moved from a standalone repository into a marketplace layout. Use this when you need to verify path rewrites, manifest identity, registry metadata, changelog/version drift, hook runtime assumptions, copied assets, tests, examples, utilities, and migration notes before publishing a marketplace package. Ask for a "marketplace migration review", "plugin import audit", "path adaptation check", or "marketplace readiness review" to use this workflow.

Targeted review of failure modes, hidden dependencies, limits, and operational burden in a specific architecture or design. Use this when you need a focused risk assessment without running a full complexity mapping — to identify single points of failure, blast radius concerns, hidden coupling, and operational survivability gaps. Produces a Hidden Risk Summary with dependency risk matrix, compound failure scenarios, and prioritized remediation actions. Ask for an "architecture risk review", "failure mode analysis", or "dependency risk assessment" to use this workflow.

Surface hidden complexity, risks, dependencies, and likely project blow-up points in a proposed design or architecture. Use this when you have architecture docs, design proposals, or technical specs and need to identify where operational, cost, networking, or implementation complexity is hiding before committing resources. Produces a Complexity Heat Map and Hidden Risk Summary with source-anchored evidence and severity ratings. Ask for a "complexity map", "hidden risk analysis", "blow-up point review", or "complexity audit" to trigger this workflow.

Split large or varied source material across parallel subagents for extraction before synthesis. Use this when documentation exceeds what can be processed in a single pass — typically more than 5 dense documents or 50+ pages — or when material spans multiple distinct domains. Produces structured Context Packets that can feed into complexity-mapper, decision-brief, or architecture-risk-review. Ask to "shard documents", "split for parallel extraction", or "break this into digestible chunks" to use this workflow.

Package extracted findings into a compact, decision-ready format for engineers, managers, or review bodies. Use this after running complexity-mapper, architecture-risk-review, or context-sharding to synthesize findings into a structured brief with options, evidence, risks, and recommended next steps. Produces a Decision Brief with evidence summary, top risks, unresolved questions, and actionable recommendations. Ask for a "decision brief", "decision package", or "summarize findings for a decision" to use this workflow.

Generate high-quality first drafts by adapting prior proven work to new problems. Use this when you have successful prior designs, implementations, or architectural patterns and need a strong starting point for a new but related problem. Produces a Pattern Remix Draft that maps reused elements to their sources, flags carried assumptions, identifies divergence risks, and provides implementation steps. Ask to "remix a prior design", "adapt existing work", or "create a first draft from prior patterns" to use this workflow.

Manage the fakoli-plugins marketplace. Use when: (1) adding a new plugin to the marketplace, (2) removing a plugin, (3) validating plugins, (4) regenerating registry indices, (5) checking marketplace status, or (6) any plugin registry management task. Triggers on phrases like "add plugin", "validate plugins", "update registry", "marketplace status".

Generate and modify Excalidraw diagrams from natural language and code analysis using skeleton JSON and a Node.js converter

This skill should be used when coordinating multiple fakoli-crew agents on a single project — assembling crews, planning waves, assigning file ownership, or routing work across guido, critic, warden, scout, smith, welder, herald, keeper, and sentinel. Provides wave patterns, file-ownership rules, status-file protocol, and language-style references shared across the crew. Trigger phrases: "assemble a crew", "who owns this file", "plan the waves", "run the crew on X", "coordinate agents to Y", "which agent should handle", "multi-agent orchestration". Each agent writes its status to the path the orchestrator provides; the default scratch root is `.fakoli/runs/<run-id>/`.

This skill should be used when a test is failing inexplicably, when a runtime error appears in production, when a bug reproduces unpredictably, or when two or more prior fix attempts have failed. Provides a 4-phase systematic debugging workflow — investigate, analyze patterns, form hypothesis, fix with test — to prevent random-fix loops. Trigger phrases: "why is this failing", "this test keeps failing", "I've tried three fixes", "root cause", "systematic debugging".

Use this skill when adding, updating, validating, or reporting on the governed Fakoli operating-model principles ledger.

Google Workspace Admin SDK: Audit logs and usage reports.

Security rules for AI agents using gws — input validation, path safety, URL encoding, and Model Armor sanitization.

Authenticate and manage credentials for the gws CLI — login, logout, status, scopes, service accounts, and credential storage.

Google Calendar: Show upcoming events across all calendars.

Google Calendar: Create a new event.

Google Calendar: Manage calendars and events.

Google Chat: Send a message to a space.

Google Chat: Manage Chat spaces and messages.

Google Classroom: Manage classes, rosters, and coursework.

Read and write Google Docs.

Google Docs: Append text to a document.

Google Drive: Manage files, folders, and shared drives.

Google Drive: Upload a file with automatic metadata.

Google Workspace Events: Renew/reactivate Workspace Events subscriptions.

Subscribe to Google Workspace events.

Google Workspace Events: Subscribe to Workspace events and stream them as NDJSON.

Read and write Google Forms.

Gmail: Forward a message to new recipients.

Gmail: Reply-all to a message (handles threading automatically).

Gmail: Reply to a message (handles threading automatically).