
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases. Credits: Original skill by @blader - https://github.com/blader/humanizer
Best practices for Remotion - Video creation in React
Manage and navigate Obsidian vault with consistent structure, naming conventions, and linking patterns
Use this skill when working with Jira tickets (RD-XXXX) to ensure proper task tracking and state persistence in `br`.
Shared orchestrator behavior for delegation-first agents. All specialized agents must follow this protocol when delegating work.
Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.
Preserve and apply the user's unique bilingual French/English communication style. Use when drafting, editing, or refining communications to maintain casual-professional tone, code-switching patterns, and specific formulas. Key elements: (1) Bilingual structure (French base + English technical terms), (2) Casual but professional tone ("je suis preneur", "je capte pas", "ça devrait rouler"), (3) Structured flow (context → technical details → questions → sign-off), (4) Strategic emoji usage (🙏, 😅), (5) Direct mentions of @people and technical context
Interact with Dagster data orchestration platform running locally or on Kubernetes. Use when Claude needs to monitor Dagster runs, get run logs, list assets/jobs, materialize assets, launch jobs, or debug pipeline failures. Supports both local Dagster dev server and Kubernetes deployments where each job run is a separate pod.
This skill should be used when performing local data exploration, profiling, quality analysis, or transformation tasks using DuckDB. It handles CSV, Parquet, and JSON files, provides automated data quality reports, supports complex JSON transformations, and generates interactive HTML reports for data analysis.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
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 be used when users need to create Jira tickets for the RD (Research & Development) project. It supports creating features, bugs, and tasks with proper field mapping including assignee, team, sprint, and state. The skill uses Jira CLI commands and provides templates for different ticket types.
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Generates intelligent GitLab merge request descriptions from git commits with automatic categorization and Jira integration
Tracks and monitors GitLab merge request activity including comments, status, and real-time updates
Manage daily notes in Obsidian vault with consistent structure
Use this skill when creating, modifying, or understanding OpenCode commands stored in `~/.config/opencode/command/`.
This skill should be used when creating, modifying, or debugging OpenCode plugins. It provides the complete plugin architecture, available hooks, event types, SDK client methods, and best practices learned from real-world plugin development.
Guide for activating pyenv virtual environments with troubleshooting for common issues
Transform learning content (like YouTube transcripts, articles, tutorials) into actionable implementation plans using the Ship-Learn-Next framework. Use when user wants to turn advice, lessons, or educational content into concrete action steps, reps, or a learning quest.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Frontend testing with browser automation, assertions, and visual regression. Use when testing web UIs, validating user flows, checking responsive design, form submissions, login flows, or detecting visual regressions. Supports dev server auto-detection, assertion collection, and screenshot comparison.
This skill should be used when generating a detailed implementation plan from an existing PRD and codebase research. It synthesizes requirements with codebase context into actionable, bite-sized TDD tasks suitable for junior developers.
This skill should be used when executing an approved implementation plan with batch checkpoints. It implements tasks in batches of 3, stops for review after each batch, and handles mismatches or blockers by asking for guidance rather than guessing.
This skill should be used when writing or reviewing Python tests. It enforces a dummy-class pattern over unittest.mock, requiring all test dependencies to use explicit dummy classes instead of Mock, MagicMock, AsyncMock, or patch().
This skill should be used when encountering any bug, test failure, or unexpected behavior. It requires finding root cause before proposing fixes. Random fixes waste time and create new bugs.
This skill should be used when conducting comprehensive codebase research to answer questions, understand architecture, or prepare context for implementation planning. It spawns parallel sub-agents and synthesizes findings into a structured research document.
This skill should be used when reviewing code changes in a branch against main/master/develop. It analyzes commits, integrates JIRA ticket and MR context when available, and produces a structured code review using Conventional Comments format.
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.
Comprehensive OpenTUI skill for building terminal user interfaces. Covers the core imperative API, React reconciler, and Solid reconciler. Use for any TUI development task including components, layout, keyboard handling, animations, and testing.
Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
Automate daily note wrapup workflow. Interview for next episode, extract learning ideas, create concept notes. Use when daily wrapup, end of day or wrapup is mentioned by user.
This skill should be used when users need to fetch Jira ticket content using either a specific ticket ID (like RD-3891) or search for tickets by title/description. It defaults to searching within the current sprint but can extend to all tickets when needed. The skill uses the Jira CLI to retrieve ticket details, status, assignee, and descriptions.
Rigorous problem decomposition and evidence-based analysis methodology for software engineering tasks. Use to analyze situations, figure out concepts or investigations.
Python conventions, patterns, and workflows. Use when writing code, reviewing PRs, or setting up new Python projects.
Requirements elicitation through structured interviewing. Use when: (1) User provides vague, ambiguous, or incomplete requirements, (2) Clarification is needed before building features or writing code, (3) User says 'build X' without specifying behavior, edge cases, or constraints, (4) Translating stakeholder requests into PRDs, specs, or user stories. Triggers on phrases like 'make it better', 'add a feature', 'fix this', 'I need something that...', or any request lacking concrete acceptance criteria.
This skill should be used when about to claim work is complete, fixed, or passing. It requires running verification commands and confirming output before making any success claims. Evidence before assertions, always.
This skill should be used when creating a Product Requirements Document (PRD) based on user input. It guides through clarifying questions, explores approaches, and produces a structured PRD suitable for junior developers to implement.
This skill should be used when validating that an implementation plan was correctly executed. It verifies success criteria, runs tests, identifies deviations, and presents structured completion options including MR creation or discard.
Generate GitLab merge request descriptions from git commits with automatic categorization and Jira integration.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Guide technical communication for software developers. Covers email structure, team messaging etiquette, meeting agendas, and adapting messages for technical vs non-technical audiences. Use when drafting professional messages, preparing meeting communications, or improving written communication.