Loading...
Loading...
Found 11,921 Skills
Interactively elicits and stores the author's paper positioning so every other skill in this repo behaves context-awarely. Use when a researcher says "set up my paper profile", "ask me about my paper", "what verticals", "configure for my paper", "remember my positioning/style", or is starting a new paper and wants the toolkit tuned before drafting. Asks with sensible options about vertical/emphasis, contribution type, audience and venue tier, risk appetite, and writing preferences, then writes .paper-memory/profile.yml in the paper working directory. Explains how downstream skills consume it for benchmark-paper weighting, simulate-reviewers persona calibration, polish-prose/match-style register, and tailor-to-venue framing. Bundles a stdlib script profile_io.py that reads/writes/validates the file and emits a blank template. Local-only, never uploaded; advisory copilot, never submits.
Renders the paper-workspace (outputs + lifecycle progress) into a single self-contained HTML dashboard the author can open in a browser, and refreshes it on request. Use when a researcher says "show me an HTML view", "give me a dashboard", "can I see my progress in a browser", "visualize what's been done", "make an HTML report", or "update the dashboard". Offered as an option whenever a visual overview would help (it is opt-in, not generated unprompted), and re-run after each significant change so the page stays current. The output is one local dashboard.html with inline CSS — no network, no external assets, light/dark aware — listing every generated artifact by stage with clickable links and a recent-activity timeline. Trigger words - html, dashboard, browser view, visualize progress, html report, update the html.
Promote a Factorial Code app's code from its dev workspace to its prod workspace — fcode clone the dev- workspace, remote:add the prod- workspace, pull prod's current metadata, then add and push. Use when releasing, promoting, or deploying a Factorial Code (fcode) app's dev workspace to production, or pushing a dev- workspace's code to its prod- counterpart.
Fetch and analyze Linear issue with all related context. Use when starting work on a Linear ticket, analyzing issues, or gathering context about a Linear issue.
One-time setup that maps the codebase and gathers user-provided product context to write a root PROJECT.md overview of what the project is, who it serves, how it is structured, and how it runs. Use when the user invokes $setup-project-md, says "setup project md", "create PROJECT.md", or asks for a complete project overview document at the repo root.
Run a complete repository-native, spec-anchored development loop inspired by DeepSeek Harness. Use for feature development, bug fixes, simplification, architecture, process, or testing work that changes behavior, contracts, structure, test strategy, durable formats, or decision rationale; when asked to write, review, continue, implement, reject, supersede, archive, or verify a spec/Agent Note/RFC/ADR; or when code, tests, current-state docs, and decision rationale must converge in one change. Also use for read-only spec-to-code drift checks. Do not create a spec for a purely mechanical local edit that changes none of those things.
Manage Symfony configuration with .env files, parameters, secrets vault, and environment-specific settings
Handle message failures with retry strategies, failure transport, and recovery in Symfony Messenger (Recoverable/Unrecoverable exceptions)
Analyze decisions made during implementation, review, or design work and distinguish project-wide guidance from route-specific fixes, already-documented rules, and premature patterns. Use when the user asks which lessons or decisions deserve inclusion in project documentation, wants to review proposed guidelines before approving documentation changes, or asks to update project guidance from recent work.
Orchestration mode: the fleet-manager only plans, dispatches, supervises, and reviews — all code changes are delegated to fleet-workers (matching the fleet-manager's harness, model, and effort by default) in visible herdr tabs, each in its own git worktree. Use when the user runs /fleet, says "fleet mode", or asks to orchestrate work across delegated agents. "fleet off" deactivates.
Use this when unexpected failures occur in tasks, when users provide corrections, when requests for missing capabilities are made, or when reusable project patterns are discovered. It is responsible for depositing high-value experiences into `.learnings/` and deciding whether to elevate them to project rules or independent skills.
Revision and editing assistant for Crucible-drafted novels. Use when author has completed a first draft and wants to revise, edit, or polish their manuscript. Handles developmental editing, line editing, copy editing, and final polish. Triggers on "edit my novel," "revise chapter X," "polish my manuscript," "help me edit," or when user has completed draft chapters and wants to improve them.