Comentaris
Comentaris i anotacions del codi
session-start
surreptakos
Re-print the start-of-session check report (remote, uncommitted work, deploy credential, tests, tickets). Use when it has scrolled out of context, or with --refresh after the tree has moved.
gaia-intake-close
gaia-research
Post-review intake closing skill. After an intake is resolved (whether accepted via review/meta PR merge or rejected/deferred at triage/evidence review), run this skill to post standardized, personalized closing comments on the PR (if any) and each intake issue. Comments include: evidence pipeline findings with /trust-appraise TM output, per-row artifact scores, decisions rationale, path-to-promotion/acceptance guidance, and a mandatory badge status note including the universal Powered by Gaia badge. Use after curation completes, before or immediately after merge for accepted intakes, or immediately upon rejection.
epic-close
gaia-research
Close out a completed EPIC / sprint end-to-end: author a fact-verified meta-post announcing what shipped, archive the EPIC's handovers, snapshot orchestrator memory, gate the integration→main merge on CI-green + explicit human go, drive the version bump (merge-commit conventions that auto-sync classifies), and verify the release reached the registry/PyPI. Use when the user says "close out EPIC <n>", "wrap up the sprint", "ship the meta shift", "/epic-close", or asks to finalize an integration branch that is ready to merge to main. Generalizes the EPIC 1002 (Yggdrasil II) close-out. This skill orchestrates — it authors founder docs directly (superadmin) and delegates code/regen to workers; it NEVER merges to main without the human gate.
Production discipline — the baseline layer
sayam
Enforced in the reference: tests/test_workflow_validity.py
core
nitedani
"Load first for any multi-step or GitHub task: the task, triage and tiers, principles, tracking, discovery, safety on the user's machine, pre-flight."
co-review
taloncjones
Freeze a finished change, collect two or four independent review seats by change class, and evaluate one fail-closed final-gate report.
erw-add-connector
SamuelEnrique
Use this skill when asked to add a new ISO, market, node set or other data source to the Energy Research Warehouse (ERW) price connector, for example "add PJM", "add ERCOT load zones", "add IESO prices", "pull another market", or "wire a new source into the daily refresh". Covers the function in warehouse/connectors/iso_prices.py, raw file saving, the completeness rule, table naming, the validator, coverage, the daily workflow and the session report, plus the mistakes earlier sessions made.
carve-authoring
markup-carve
Use when writing or editing Carve markup (.crv / .carve files), or when the user asks to author Carve. Carve is a post-Markdown lightweight markup language that deliberately diverges from Markdown/Djot — the emphasis delimiters are swapped (/italic/, bold), sup/sub are braced-only, and several Markdown habits produce wrong output. This skill front-loads the correct syntax and the traps so the output is valid Carve the first time.
pitlane
laneworkapp
"Pitlane / Lanework board operations — reading and writing cards and comments on Lanework kanban boards (plain folders + Markdown rendered live by the Lanework app; the files ARE the board, no API); by default, a project keeps a Pitlane/ folder at its repo root holding <Project> Pipeline.lanework, and ~/Pitlane holds machine-level boards; and agentic board sweeps: sweeping a pipeline board for workloads, triaging them, and farming the work out to model-tiered subagents with a lead/fixer/reviewer split. Use this skill whenever the user mentions Lanework, Pitlane, a pipeline board (e.g. 'Acme Pipeline', 'Lab Pipeline'), sweeping or working a board, filing/moving a card, posting a board comment, triaging Ideas, answering board questions, or working the Approved lane — 'sweep the pipeline board', 'check the lab board', 'file a card on the lab board', 'any open questions on the boards?', 'work the approved cards'. Not for generic kanban/project-management advice unrelated to Lanework boards."
open-source-contributor
wahajahmed010
"Autonomous GitHub contribution agent using the Architect-Builder pattern. Buck (main agent) handles all git/network I/O; subagents handle focused cognitive work only. Scouts issues, implements fixes, and submits PRs. Supports three difficulty levels. Triggers on: open source, github, contribution, PR, pull request, issue fix, OSS, contributor."
comment-loop
meech-ward
Work through the open comments people left on notes, drawings and diagrams in an elaborat.ing project. Makes each requested change and replies in the thread; the person resolves it. Use when the user asks to address, answer or work through comments, review feedback or requested changes in elaborat.ing.
consistency-sweep
dacekroberts
Audit what the build and research sessions leave behind - stale prose written in the future tense, hand-kept counts that drifted, cross-references broken by renumbering, sources in use with no licence read, tables that stopped rendering, orphaned branches and worktrees. Use when asked to check whether the project's own documents are still true, to clean up after a city or country landed, or when a session is claiming the cleanup role. Not for building a city (add-city) or screening one (add-country).
capabilities-map
Atrium-Hermes
Weekly read-only audit of installed skills' capability coverage — maps every enabled/disabled skill against the locked 6-value taxonomy in docs/CAPABILITIES.md, flags any capability tier with zero enabled coverage as an actionable gap
flutter-widget-previewer
ab22593k
Use the Flutter Widget Previewer to preview widgets in isolation with real-time rendering in Chrome. Use when working with Flutter widget previews, @Preview annotations, preview configurations, or widget development workflows. Triggers include setting up widget previewer, adding @Preview annotations, customizing previews, creating custom preview annotations, handling multiple preview configurations, or troubleshooting widget preview issues.
code-comments
idotta
Write clear, plain-spoken code comments and documentation that lives alongside the code. Use when writing or reviewing code that needs inline documentation—file headers, function docs, architectural decisions, or explanatory comments. Optimized for both human readers and AI coding assistants who benefit from co-located context.
file
zheref
File one well-formed, correctly-labelled, non-duplicate issue — reconciling it against the open backlog first. Use when the maintainer invokes hatsu:file <problem> <repo> or a bare hatsu:file (which files what the session has just been discussing), or asks to file, open, log or raise an issue. Also execute the shared discovery protocol when authorized work exposes a durable workflow, machinery, or owner gap. Process-chairman findings — constitution, canon prose, machinery enhancement, duration, redundancy, autonomy gaps, deterministic jobs still done by hand, missing toolchain — are Netero's completeness contract (claude/agents/netero.md; Codex: the Netero section of AGENTS.md): every declared classifying label, observable acceptance criteria, and cross-references for deployment, fan-out and provisioning. Kurapika searches for duplicates to amend, near-neighbours to fold into, and issues this supersedes before writing.
gh-body-file
simnova
Never pass issue/PR/comment text to gh via --body "...". Backticks in the string are shell command substitution and silently mangle the published body. Always --body-file from a quoted heredoc, then verify.
todoist-triage
surreptakos
"Triage Dan's Todoist work tasks. Use for the daily or Friday pass, clearing the backlog, or deciding what to delegate."
what-needs-me
coalesce-labs
The human's decision inbox on Catalyst Cloud, and the one way an agent raises a decision on their behalf. Use when the person asks "what needs me?", "what am I blocking?", or when active work is gated on a choice only they can make. Lists open asks ranked by how much open work each one holds, files an ask through the cloud's ask route with the account's own template, and records the answer so the held work releases. Never answers as the human, never duplicates an open ask.
docx
nicolasganan
"Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation."
code-fact-check
magfrump
Verify checkable claims in code comments, docstrings, commit messages, and project documentation against actual code behavior. This is the code analog of the prose fact-check skill: where fact-check checks essay claims against the world via web search, code-fact-check checks code claims against the codebase via direct file reading — and, when a claim's subject is executable in the review sandbox, by actually running it. For every claim about what code does, how it performs, or how it's structured, search the codebase for evidence and report findings with calibrated confidence. Produces a structured Markdown report. Use this skill when the user asks to "verify the comments", "check the docs against the code", "audit documentation accuracy", "are the docstrings still accurate", "do the comments match the code", or when upstream orchestration (e.g., the code-review skill) requests a code verification pass. Also trigger when reviewing or onboarding to a codebase and the comments or docstrings look stale, drifted, or contradict the surrounding implementation — running this skill before further work surfaces documentation rot that would otherwise mislead later changes.
plain-language
ggwicz
Reviews project text — documentation, READMEs, marketing copy, UI strings, code comments, error messages — for compliance with the U.S. federal government Plain Language Guidelines. Produces structured edit recommendations with concrete rewrites. Activates on plain language review, readability check, copy audit, "make this clearer," or "improve the writing."
vercel-composition-patterns
011matthias
React composition patterns that scale. Use when refactoring components with
wp-block-markup
bph
Convert Markdown files to WordPress block markup (Gutenberg serialized HTML). Use whenever the user wants to produce content that can be pasted into the WordPress Code Editor or used in block theme HTML templates. Also use for the reverse direction (block markup to markdown).