
Use when choosing or configuring Python logging, especially deciding between stdlib logging and loguru for apps or CLIs.
Inspect all pull-request feedback, verify each claim, make and test bounded local fixes, and prepare focused commits, replies, thread resolutions, and a push. Use only when the user explicitly invokes $resolving-pr-review-comments or names resolving-pr-review-comments; public replies, resolutions, and pushes still require exact approval.
Switch a clean Git worktree to local `main` and fast-forward it from its configured upstream without losing branches, commits, or local files. Use only when the user explicitly invokes $syncing-main-branch or names syncing-main-branch.
Decide whether IMRaD fits, review an IMRaD draft, transform mixed material into IMRaD, or draft a new evidence-traceable IMRaD output without fabricating results.
Iteratively audit and improve an existing web interface with Chrome DevTools by planning, implementing, validating, and locally committing one evidence-backed UI/UX improvement at a time. Use only when the user explicitly invokes `$iterating-ui-improvements` or names it to request an autonomous audit-fix-commit loop.
Create, inspect, attach, repair, remove, or prune local Git worktrees while preserving branches, detached commits, and tracked, untracked, ignored, and submodule data. Use for the full worktree lifecycle or optional branch cleanup.
Use only when the user explicitly names the writing-work-logs skill; never auto-activate from generic work log, daily log, EOD summary, status update, or date-range summary requests.
Use when inspecting local git changes, drafting or validating Conventional Commit messages, checking type or scope choices, explaining breaking changes, or creating a focused commit from the actual diff.
Choose, review, rename, and standardize agent skill names so they are predictable, searchable, and easy for agents to select correctly. Use when creating a new skill name, renaming an existing skill, reviewing whether a skill name is appropriate, standardizing multiple skill names, converting informal skill ideas into production-ready skill names, or designing naming conventions for an agent skill library.
Use when deciding whether IMRaD fits, drafting a fresh IMRaD output, transforming mixed material into IMRaD, or reviewing an IMRaD draft for structure, evidence, and section-boundary correctness.
Use when auditing Atuin shell history for noisy duplicates or high-confidence typo/retry pairs and when preparing safe preview-first cleanup steps without editing the SQLite database directly.
Use when implementing non-trivial code changes that should follow TDD (write a failing test first, make the smallest passing change, then refactor safely).
Use when designing, implementing, reviewing, or debugging Codex CLI hooks, including `hooks.json`, `.codex/hooks.json`, feature-flag setup, matcher behavior, event-specific stdin/stdout payloads, and hook scripts for `SessionStart`, `PreToolUse`, `PostToolUse`, `UserPromptSubmit`, or `Stop`.
Use when a task involves Python project setup or standalone scripts with uv, including dependency management, `uv run`, `uv run --with`, `--no-project`, inline script metadata, quality gates (ruff, ty, pytest, coverage, prek/pre-commit), and package build or publishing workflows.
Use when interacting with Jira through ankitpokhrel/jira-cli (`jira`), including setup, authentication, issue queries, issue creation or edits, transitions, comments, worklogs, epics, sprints, releases, projects, boards, and script-friendly output.
Use when building or structuring Python CLI commands with Typer, including commands, options, and multi-command apps.
Use when working with Peewee ORM patterns, especially DatabaseProxy setup, scoped connection/transaction handling, and SQLite-based tests.
Run iterative multi-reviewer panels over a code diff, verify their findings, apply explicitly authorized fixes, and re-review the updated change until it passes or reaches a stopping condition. Use when the user asks for a panel loop, multi-model code-review consensus, or a review-fix-re-review cycle.
Use when implementing a non-trivial behavior change with Test-Driven Development (TDD) when practical: prove a focused failure, make the smallest passing change, then refactor safely.
Choose, review, rename, and standardize agent skill names so they are predictable, searchable, and easy for agents to select correctly. Use when creating a new skill name, renaming an existing skill, reviewing whether a skill name is appropriate, standardizing multiple skill names, converting informal skill ideas into production-ready skill names, or designing naming conventions for an agent skill library.
Use when creating or updating city-based gourmet research outputs that require multi-source evidence, standardized scoring, and structured audit files.
Use when implementing non-trivial code changes with Test-Driven Development (TDD): write a failing test first, make the smallest passing change, then refactor safely.
Creates and maintains concise repository MEMORY.md notes for gotchas, stale memory corrections, and durable user preferences. Use at the start of repository conversations, when the user mentions MEMORY.md, when an error or preference should be remembered for future work, when MEMORY.md content may be wrong, or when the first qualifying memory emerges in a repository that has no MEMORY.md yet.
Use when you need SVG diagram rules, layout patterns, or embedding guidance for slide decks and want the minimal SVG-focused reading path.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when the user wants to get grilled on a design, stress-test a plan, or mentions "grill me".
Use when deciding whether IMRaD fits, drafting a fresh IMRaD output, transforming mixed material into IMRaD, or reviewing an IMRaD draft for structure, evidence, and section-boundary correctness.
Use when you only need slide color systems, palette selection, or palette generation workflows and want direct pointers to the color design references.
Use when reviewing code changes for correctness, maintainability, readability, security, performance, test coverage, and integration risk; especially when the user asks to inspect a diff, pull request, merge request, commit, patch, or source files.
Assess or improve an existing codebase's architecture when the user asks about module boundaries, coupling, scattered ownership, testability, change locality, deep modules, seams, or behavior-preserving structural refactoring. Use for cross-module design rather than ordinary diff review or a confirmed edge-case bug fix.
Score or compare one or more agent skills across trigger clarity, workflow actionability, safety boundaries, verification rigor, incremental knowledge value, and leanness. Use only when the user explicitly asks for ratings, numerical quality scores, rubric-based scorecards, or scored comparisons; use creating-agent-skills for unscored reviews or revisions.
Review diffs, pull requests, commits, patches, or source files for correctness, baseline security, performance, maintainability, tests, and integration risk. Use for ordinary read-only review, edge-case audits, PR preflight, and reviewer simulation; use auditing-code-security when security is the primary objective, and hardening-code-paths to fix confirmed failure modes.
Run one-shot Google Gemini research through the official Google GenAI Interactions API with Google Search, Google Maps, or URL Context grounding and inspect citation evidence. Use when Codex needs current web grounding, place or local recommendations, answers about specific public HTTP(S) URLs, or an explicit Gemini/Google GenAI grounded response.
Perform read-only security audits, vulnerability assessments, or threat-focused reviews of diffs, pull requests, code paths, or explicitly scoped repositories when security is the primary objective or acceptance criterion. Use reviewing-code for ordinary review with baseline security coverage and hardening-code-paths for fixing confirmed findings.
Use when asked to proactively harden a specific code path by confirming and fixing plausible edge-case, boundary, failure-mode, or lifecycle bugs; to fix a confirmed security finding; or to check nearby same-pattern regression risks. Use auditing-code-security first for broad threat analysis or unverified security alerts.
Design or redesign end-to-end user experiences for new or existing digital products through an approval-gated workflow. Use for substantial work on user goals, information architecture, navigation, workflows, system states, or interaction behavior that requires a proposal before implementation.
Prepare and publish one explicitly authorized public Telegra.ph article through the official Telegraph API, including safe node conversion, optional account setup, credential handling, and page verification.
Audit Atuin history for duplicate pressure and high-confidence typo/retry pairs, then prepare fixed-scope deduplication or user-run inspector steps without direct SQLite deletion. This deprecated internal workflow keeps cleanup-typos disabled.
Use when interacting with Jira through ankitpokhrel/jira-cli (`jira`), including setup, authentication, issue queries, issue creation or edits, transitions, comments, worklogs, epics, sprints, releases, projects, boards, and script-friendly output.
Use when the user asks for a detailed, beginner-friendly, or step-by-step explanation; wants to understand how or why something works; asks to unpack a concept, issue, PR, code change, system, error, document, or technical decision; or says to explain it like teaching a child.
Create and publish public Telegra.ph articles through the official Telegraph API, including account setup, content conversion to Telegraph nodes, credential handling, and publication verification. Use when the user asks to create, publish, or post a page or article on telegra.ph.
Switch a clean Git worktree to the local main branch and fast-forward it from its configured upstream. Use only when the user explicitly invokes $syncing-main-branch or names syncing-main-branch; never auto-activate from ordinary requests to switch branches, return after a merge, pull, update, or sync a repository.
Inspect all feedback on a pull request, assess whether each comment is valid against the current code, address reasonable findings, verify the changes, reply to and resolve eligible threads, commit, and push. Use only when the user explicitly invokes $resolving-pr-review-comments or names resolving-pr-review-comments; never auto-activate from ordinary requests about reviews, comments, pull requests, commits, or pushes.
Decide when to check command help before running shell or CLI commands. Use when Codex is about to execute a command and must judge whether it already understands the exact command form, flags, subcommands, or help path well enough to proceed, or should first consult `--help`, built-in `help`, `man`, or shell `help`.
Use when a task involves Python project setup or standalone scripts with uv, including dependency management, `uv run`, `uv run --with`, `--no-project`, inline script metadata, quality gates (ruff, ty, pytest, coverage, prek/pre-commit), and package build or publishing workflows.
Use when creating or updating city-based gourmet research outputs that require multi-source evidence, standardized scoring, and structured audit files.
Use when creating or converting Mermaid diagrams, including flowcharts, sequence diagrams, ER diagrams, class diagrams, state diagrams, Gantt charts, and SVG exports.
Use when you need Marp/Marpit Markdown authoring rules, directives, layouts, or theme guidance and want the minimal reading path for slide writing.
Create, update, or review agent skills with correct structure, triggering metadata, bundled resources, UI metadata, repository integration, and validation. Use when the user asks to create a new skill, improve an existing skill, turn a workflow into a reusable skill, scaffold skill files, or check whether a skill is concise, discoverable, and valid.
Use when creating slide decks with Marp/Marpit Markdown (marp), including authoring slide content, designing slide color schemes, and building SVG diagrams or illustrations for the deck.
Design, implement, and review UI/UX that minimizes cognitive load without sacrificing functional completeness, using Apple-derived design philosophy adapted to the target platform. Use when creating or evaluating screens, components, wireframes, navigation, workflows, dashboards, forms, or design systems; especially when deciding what stays visible, what uses progressive disclosure, how information should be prioritized, or whether an interface is cluttered or over-simplified.
Use when asked to proactively find, fix, or harden edge-case bugs in a specific code flow, or when a concrete bug fix suggests nearby same-pattern regression risks that should be inspected.
Use when the user asks to create, review, audit, migrate, or update an AGENTS.md file for a repository, package, subproject, or monorepo. This skill writes agent-facing repository guidance grounded in project evidence, including setup, build/test commands, code style, testing, security, PR rules, nested AGENTS.md scope, and instruction precedence.
Create, inspect, attach, repair, remove, prune, and clean up local Git worktrees safely. Use when Codex needs to manage a repository's worktree lifecycle, including creating a branch-backed worktree under worktrees/, attaching an existing local branch, repairing moved worktrees, diagnosing stale metadata, preserving detached commits and local-only files during removal, or optionally deleting a merged branch.
Draft, execute, and track lean, verifiable plans for non-trivial work. Use when the user asks for a plan, implementation plan, roadmap, design plan, migration plan, refactor plan, PR split, plan checklist, completion checklist, or execution of an existing plan; or when the task needs sequencing, tradeoffs, assumptions, unknowns, risk control, or completion criteria. Do not use for small, obvious tasks that can be completed directly.
Choose, configure, or review Python logging for libraries, services, apps, and CLIs, especially when deciding between stdlib logging and Loguru or defining handlers, levels, context, and exception behavior.
Use only when the user explicitly names writing-work-logs to produce a concise, evidence-based Git work log for a resolved date range; never auto-activate for generic status or summary requests.
Read and maintain concise repository-root MEMORY.md notes for verified gotchas, durable user preferences, and established repository conventions. Use at repository-conversation start, when MEMORY.md is mentioned or may be stale, or when a qualifying memory emerges.
Deprecated internal workflow for auditable city-based food research with multi-source evidence, scope-checked rankings, standardized scoring, and synchronized candidate, recommendation, and exclusion files.
Create or revise complete Marp/Marpit slide decks, coordinating narrative, slide authoring, color systems, and Mermaid or SVG visuals with rendered validation.
Create, review, audit, migrate, or update scoped AGENTS.md repository guidance with evidence-backed commands, concise constraints, explicit authority, instruction precedence, and verifiable completion criteria.
Deprecated compatibility reference for choosing, reviewing, renaming, or standardizing agent skill names. Use the active creating-agent-skills workflow for current naming and authorized repository rename work.
Use when the user asks for a detailed, beginner-friendly, or step-by-step explanation; wants to understand how or why something works; asks to unpack a concept, issue, PR, code change, system, error, document, or technical decision; or says to explain it like teaching a child.
Design, wire, or test Peewee ORM models with deferred database binding, scoped connections, explicit transactions, and isolated SQLite fixtures. Use for `DatabaseProxy`, model lifecycle, transaction boundaries, or Peewee-backed tests.
Design, implement, review, or debug the deprecated repository reference for Codex CLI hooks, including hooks.json layers, event matchers, stdin/stdout contracts, and hook scripts. Verify current Codex documentation before relying on version-sensitive behavior.
Build, extend, package, migrate, or test Python CLIs with Typer, including command grammar, typed arguments and options, callbacks and context, command groups, prompts, completion, entry points, and current CliRunner behavior. Use when Typer is chosen or an existing Typer CLI needs changes.
Create, revise, convert, or validate Mermaid diagrams, including flowcharts, sequence, ER, class, state, Gantt, and optional SVG rendering for documents or slides.
Write, revise, structure, or validate Marp/Marpit Markdown slides, including directives, layouts, themes, templates, and rendered-deck checks. Use for slide authoring when palette or illustration design is not the primary task.
Design, implement, or review screens, components, navigation, workflows, forms, dashboards, and design systems for clear hierarchy, low cognitive load, accessibility, and preserved capability, using Apple-derived philosophy adapted to the target platform. Use especially for visibility, progressive-disclosure, clutter, or over-simplification decisions.
Design, adapt, generate, or validate slide color systems and semantic palettes, including brand-color integration, usage roles, contrast evidence, and presentation-environment caveats.
Create, name, rename, revise, or review agent skills for reliable triggering, lean instructions, justified resources, aligned UI metadata, repository discovery, and validation. Use for new skills, naming decisions, authorized repository renames, skill scaffolding, workflow-to-skill conversion, prompt optimization, or skill audits.
Manage Python projects and standalone scripts with uv, including setup, dependencies, execution, quality gates, locking, builds, and release preparation. Use for `uv run`, `uv add`, inline script metadata, packaging, or an explicitly requested publish workflow.
Decide whether to inspect command help before execution when the exact subcommand, flags, targets, side effects, or help mechanism are uncertain.
Inspect local Git changes, draft or validate Conventional Commit messages, choose types/scopes, explain breaking changes, or create a focused commit from the actual selected diff.
Inspect Jira or prepare and perform precisely authorized Jira mutations with ankitpokhrel/jira-cli (`jira`), including issues, comments, worklogs, epics, sprints, releases, projects, boards, and script-friendly output.
Create, revise, embed, or troubleshoot accessible SVG diagrams and illustrations for slide decks, documents, and other static artifacts, with portable sizing, layout, style, and validation guidance.
Interview the user one decision at a time to stress-test a plan or design until goals, constraints, assumptions, tradeoffs, risks, and verification are explicit. Use only when the user asks to be grilled or names “grilling designs.”
Draft, execute, and track lean, verifiable plans for non-trivial work involving sequencing, tradeoffs, assumptions, unknowns, risks, or completion criteria. Use for implementation plans, roadmaps, migrations, refactors, PR splits, checklists, or execution of an existing plan; skip small obvious tasks.
Use when building or structuring Python CLI commands with Typer, including commands, options, and multi-command apps.
Use when transforming non-IMRaD material into a clean IMRaD output with strict section boundaries and explicit assumption labeling.
Use when producing research-style outputs that should follow IMRaD (Introduction, Methods, Results, Discussion).
Use when you need Marp/Marpit Markdown authoring rules, directives, layouts, or theme guidance and want the minimal reading path for slide writing.
Use when creating or updating AGENTS.md contributor guidelines for this repository.
Use when designing, implementing, reviewing, or debugging Codex CLI hooks, including `hooks.json`, `.codex/hooks.json`, feature-flag setup, matcher behavior, event-specific stdin/stdout payloads, and hook scripts for `SessionStart`, `PreToolUse`, `PostToolUse`, `UserPromptSubmit`, or `Stop`.
Use when creating or updating city-based gourmet research outputs that require multi-source evidence, standardized scoring, and structured audit files.
Use when working with Peewee ORM patterns, especially DatabaseProxy setup, scoped connection/transaction handling, and SQLite-based tests.
Use when you only need slide color systems, palette selection, or palette generation workflows and want direct pointers to the color design references.
Use when creating slide decks with Marp/Marpit Markdown (marp), including authoring slide content, designing slide color schemes, and building SVG diagrams or illustrations for the deck.
Use when you need SVG diagram rules, layout patterns, or embedding guidance for slide decks and want the minimal SVG-focused reading path.
Use when implementing non-trivial code changes that should follow TDD (write a failing test first, make the smallest passing change, then refactor safely).
Use when deciding whether IMRaD is appropriate and diagnosing which IMRaD components are explicit, partial, inferable, or missing.
Use when auditing Atuin shell history for noisy duplicates or high-confidence typo/retry pairs and when preparing safe preview-first cleanup steps without editing the SQLite database directly.
Maintains concise repository MEMORY.md notes for gotchas, stale memory corrections, and durable user preferences. Use at the start of repository conversations, when the user mentions MEMORY.md, when an error should be remembered to avoid repeating it, or when MEMORY.md content may be wrong.
Use when designing, implementing, reviewing, or debugging Codex CLI hooks, including `hooks.json`, `.codex/hooks.json`, feature-flag setup, matcher behavior, event-specific stdin/stdout payloads, and hook scripts for `SessionStart`, `PreToolUse`, `PostToolUse`, `UserPromptSubmit`, or `Stop`.
Use when reviewing an IMRaD draft for structural integrity, evidentiary support, and section-boundary correctness.
Use only when the user explicitly names the work-log-writer skill; never auto-activate from generic work log, daily log, EOD summary, status update, or date-range summary requests.
Decide when to check command help before running shell or CLI commands. Use when Codex is about to execute a command and must judge whether it already understands the exact command form, flags, subcommands, or help path well enough to proceed, or should first consult `--help`, built-in `help`, `man`, or shell `help`.
Use when inspecting local git changes, drafting or validating Conventional Commit messages, checking type or scope choices, explaining breaking changes, or creating a focused commit from the actual diff.
Use when a task involves Python project setup or standalone scripts with uv, including dependency management, `uv run`, `uv run --with`, `--no-project`, inline script metadata, quality gates (ruff, ty, pytest, coverage, prek/pre-commit), and package build or publishing workflows.
Use only when the user explicitly names the work-log-writer skill; never auto-activate from generic work log, daily log, EOD summary, status update, or date-range summary requests.
Use when building or structuring Python CLI commands with Typer, including commands, options, and multi-command apps.
Use when implementing non-trivial code changes that should follow TDD (write a failing test first, make the smallest passing change, then refactor safely).
Use when choosing or configuring Python logging, especially deciding between stdlib logging and loguru for apps or CLIs.
Use when creating or converting Mermaid diagrams (for example flowcharts, sequence diagrams, ER diagrams, and Gantt charts), including exporting to SVG for docs or slides.
Use when running or authoring standalone Python scripts with uv, especially when choosing Python versions, adding one-off dependencies, using no-project mode, or embedding inline script metadata.
Use when initializing a Python project or script, adding dependencies, or running commands with uv, especially to avoid pip install and direct python/pytest usage.
Use when building or publishing Python packages with uv, including dist artifacts and pre-publish checks.
Use when configuring or running Python quality tools (ruff, ty, pytest, coverage, CI gates) and when enforcing a pre-merge quality checklist.
Use when deciding whether IMRaD fits, drafting a fresh IMRaD output, transforming mixed material into IMRaD, or reviewing an IMRaD draft for structure, evidence, and section-boundary correctness.
Use when auditing Atuin shell history for noisy duplicates or high-confidence typo/retry pairs and when preparing safe preview-first cleanup steps without editing the SQLite database directly.
Use the `gurume` CLI to search Japanese restaurants on Tabelog. Trigger this whenever the user wants to find, recommend, or research restaurants/eateries in Japan — by area (Tokyo, Osaka, Kyoto, 三重, etc.), by cuisine (ramen, sushi, yakiniku, izakaya...), or with a vague request like "where should I eat in Shibuya" or "any good unagi spots near Tokyo Station". Use this even when the user does not explicitly mention Tabelog or the `gurume` tool, as long as the intent is finding Japanese restaurants.
Load URL content as text or markdown with kabigon. Use this for extracting content from YouTube videos, social posts, news articles, PDFs, GitHub files, generic web pages, and audio/video URLs through kabigon's automatic Pipeline planning.
A URL content loading tool that extracts text or metadata from URLs across multiple platforms (YouTube, PTT, Twitter/X, Truth Social, Reddit, GitHub, and more). Use this when you need to load and extract content from social posts, videos, documents, or code repositories for scraping, data extraction, or content analysis.