All Skills

Edit PDFs with natural-language instructions using the nano-pdf CLI.

Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.

Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linking related objects, enforcing constraints, planning multi-step actions as graph transformations, or when skills need to share state. Trigger on "remember", "what do I know about", "link X to Y", "show dependencies", entity CRUD, or cross-skill data access.

`task-agent`/`review-agent`: use when CPU, memory, I/O, database, network, rendering, or cost needs measured bottleneck evidence; skip without a profiling need.

`analysis-agent`/`task-agent`/`review-agent`: use when code needs correctness, security, performance, maintainability, or hallucinated-API review; skip when no review is needed.

`analysis-agent`/`task-agent`/`review-agent`: use when a critical assembled journey needs proof unavailable below E2E; skip risks proved by component, seam, or contract tests.

`analysis-agent`/`task-agent`/`review-agent`: use when logic, rules, invariants, branches, edges, or failure paths need isolated tests; skip without a unit-test decision.

`analysis-agent`/`task-agent`/`review-agent`: use for render sinks, browser state, server fetch, upload, redirect, cross-origin, or embedding changes; skip without web exposure.

Use `analysis-agent` to create a Task DAG from an accepted source-backed Brief when 2+ tasks have dependencies, parallel value, integration, or release order. Skip single edits, accepted DAGs, and unanalysed requests.

Use `analysis-agent` to map acceptance to validation, `task-agent` to add or run bounded tests, and `review-agent` to assess proof coverage. Skip work with no material change or already-fresh complete validation.

For analysis/task/review agents using a Professional Skill on models, RAG, agents, evaluation, or safety; not for work without AI decision impact.

`task-agent`: use when document, key-value, wide-column, or graph storage changes access, partitioning, consistency, or evolution; skip vendor-only mentions and unchanged storage.

Use `task-agent` for bounded logging changes or `review-agent` to independently assess placement, schema, severity, redaction, correlation, and signal tradeoffs. Skip work with no logging impact and self-review requests.

Dispatch-only.

For analysis/task/review agents using a Professional Skill on devices, firmware, edge protocols, updates, or safety; not for work without device, firmware, or physical impact.

`task-agent`/`review-agent`: use when image layers, build context, runtime user, secrets, health checks, shutdown, or provenance change; skip when container behavior is unaffected.

`analysis-agent`/`task-agent`/`review-agent`: use for provider-consumer compatibility of APIs, events, schemas, or behavior; skip without independent consumer/version risk.

`analysis-agent`/`task-agent`/`review-agent`: use for component, route, browser, accessibility, and API-backed UI-state tests; skip backend, portfolio, and release-verdict work.

Use when tenant isolation spans data, caches, queues, runtime, search, telemetry, deletion, or export. Skip policy-only authorization, billing, customization, and SaaS lifecycle.

`analysis-agent`/`task-agent`: use for persisted identity, relationship, ownership, lifecycle, cardinality, or invariants; skip repository, migration, and mapping-only work.

`task-agent`: use when DTO fields, validation, nullability, defaults, serialization, or compatibility change; skip persistence/domain-only work without an external schema.

`analysis-agent`: use when actors, goals, preconditions, triggers, paths, guarantees, postconditions, or acceptance traces need modeling; skip when no use-case decision exists.

Use `analysis-agent` for release decisions, `task-agent` for delivery artifacts, or `review-agent` for readiness on deployment, migration, rollback, or production risk. Skip local work with no release decision.

Use `analysis-agent` to identify domain ownership, invariants, state transitions, and cross-context effects when rules change or ownership is unclear. Skip presentation-only or question-only work with no domain behavior.

Use when an installed-client change has a confirmed macOS target and changes Apple desktop platform behavior.

`task-agent`/`review-agent`: use when a Kubernetes workload, route, identity, health, capacity, or rollout boundary changes; skip image-only, pipeline-only, and non-cluster work.

`analysis-agent`/`task-agent`/`review-agent`: use for recurrence guards on known defects, incidents, or escaped failures; skip speculative risk without a prior failure mechanism.

Use `analysis-agent` when engineering intent lacks desired behavior, boundaries, constraints, or completion signals. Skip requests with an accepted Engineering Brief and no-repo direct-answer work.

Use an independently assigned `review-agent` for post-authoring review of changed rd-skills routing registries, fixtures, mappings, or owner conflicts without repair. Skip product work and in-task global rerouting.

For analysis/task/review agents using a Professional Skill on batch, stream, warehouse, lineage, replay, or data quality; not for transactions without distributed-data impact.

`analysis-agent`/`task-agent`/`review-agent`: primary-Skill-selected for races, locks, optimistic conflicts, or worker overlap; never task owner; skip without concurrency impact.

`analysis-agent`/`task-agent`: use when tokens, components, responsive behavior, accessibility, or variants need consistency rules; skip when UI system rules are unaffected.

`analysis-agent`/`task-agent`/`review-agent`: use for database, broker, cache, HTTP, framework, process, or transaction seam proof; skip local, portfolio, and release-verdict work.

Use `task-agent` for bounded frontend component or browser changes involving interaction, accessibility, API failures, security, or regression proof. Skip backend-only work and design exploration without implementation.

Use `review-agent` for a high-risk Engineering Brief when a critical path, architecture boundary, material risk, or multiple downstream tasks need deeper design evidence. Skip ordinary work without those signals.

Use when an installed-client change has a confirmed Android target and changes Android platform behavior.