Other Skills

Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.

Parse and analyze CSV files with data validation

Create HTML dashboards with KPI metric cards, bar/pie/line charts, progress indicators, and data visualizations. Use when users request dashboards, metrics displays, KPI visualizations, data charts, or monitoring interfaces.

Execute detailed plans in batches with review checkpoints

Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches

Analyze files and get detailed metadata including size, line counts, modification times, and content statistics. Use when users request file information, statistics, or analysis without modifying files.

Generate testable hypotheses. Formulate from observations, design experiments, explore competing explanations, develop predictions, propose mechanisms, for scientific inquiry across domains.

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

This skill should fail parsing because it's description field is misspelled.

This skill should fail validation because it has no description.

This skill is missing the required name field

This skill should fail parsing due to malformed YAML frontmatter.

This skill has malformed YAML syntax and should fail to parse.

Flip core assumptions to reveal hidden constraints and alternative approaches - "what if the opposite were true?"

Parse and validate JSON data with schema support

Work with Linear issues via CLI - use this skill whenever the user asks about Linear issues, creating, updating, commenting on, or deleting issues, or checking issue status and details

Creates ADRs (Nygard format, 7 sections, ~300-500 words) via short Q&A. Assigns next ADR number and validates standards.

Orchestrates Story tasks. Prioritizes To Review -> To Rework -> Todo, delegates to ln-331/ln-333/ln-334, hands Story quality to ln-340. Metadata-only loading up front.

Executes implementation tasks (Todo -> In Progress -> To Review). Follows KISS/YAGNI, guides, quality checks. Not for test tasks.

Reviews a single task in To Review and decides Done vs To Rework with immediate fixes or clear rework notes. - Load full task and parent Story; understand AC, context, and Technical Approach. - Check architecture, correctness, configuration hygiene, docs, and tests. - For test tasks, verify risk-bas...

Fixes tasks in To Rework and returns them to To Review. Applies reviewer feedback only for the selected task.

Worker that checks DRY/KISS/YAGNI/architecture/guide compliance for Done implementation tasks. Reports issues; does not change statuses or create tasks.

Spot patterns appearing in 3+ domains to find universal principles

This skill is missing the required name field