skills

Explain this fixture repository's established installable-skill layout. Use only for repository-layout orientation.

Diagnose a failed release from logs, status output, and repository state.

Validate and publish an authorized release after resolving its repository and environment.

TODO: describe when this package-checking skill should trigger

Review proposed code changes for correctness and maintainability.

Draft changelog entries from merged changes and release metadata.

Validate and publish an authorized release after release notes are approved.

Orient release operators to the correct installable skill.

Write changelog copy from merged pull requests and issue metadata.

Draft release notes from merged changes and issue metadata.

Publish a release after its notes and artifacts are approved.

Orient operators to published release skills.

Helps with releases, publishing, shipping, setup, debugging releases, fixing publish problems, and anything related to releasing. Use whenever release, publish, ship, deployment, setup, or debugging is mentioned.

Audit installable skill packages for release-blocking structure and verification gaps.

Orient users to published installable skills.

Call the Orbit provider API to inspect projects and deployments.

Retired notification helper retained temporarily for migration history.

Audit notification configuration and delivery evidence without sending messages.

Orient users to published notification skills.

Review source changes for correctness, maintainability, and regression risk.

Review source changes for quality problems.

Run the repository's required review checks before release.

Orient users to published review skills.

Analyze application logs, debug log problems, inspect output, and help with anything related to logs.

Create, harden, and curate production-grade installable skills and skill libraries. Use for API/CLI/reference skills, invocation design, progressive disclosure, evals, placement, promotion, renames, deprecation, or catalog/router consistency. Skip trivial one-file utilities.

Passive guidance for maintainable code: decomposition, readable names, safe defaults, side-effect guardrails, compatibility, quality gates, and useful comments. Use when writing, editing, refactoring, reviewing, or planning production code, CI, scripts, configuration, tests, or technical debt. Skip non-code writing and disposable experiments.

Passive guidance for maintainable tests that document behavior, isolate side effects, prove compatibility, and resist false positives. Use when writing, editing, refactoring, reviewing, or planning tests, fixtures, mocks, regression coverage, harnesses, edge cases, or testability changes. Skip non-code writing and disposable experiments.

Prevent bloated text scaffolds in new web pages. Use when creating or refactoring landing pages, SaaS pages, dashboards, marketing sections, UI copy, placeholders, labels, eyebrow text, or feature cards. Remove generic labels unless explicitly requested. Do NOT use for prose-only articles, legal copy, or exact client-provided copy.

Passive production-app resilience skill for self-healing apps. Use when coding or reviewing features with jobs, queues, webhooks, persistence, APIs, retries, concurrency, logging, tracing, observability, incidents, edge cases, failsafes, idempotency, backpressure, graceful degradation, or stuck jobs. Do NOT use for non-code writing, throwaway scripts, or visual-only mockups.

Passive skill enforcing strong typing when writing or reviewing PHP, TypeScript, Python, C#, Kotlin, Go, Rust, or other typed code. Bans any/mixed, untyped signatures, blind ??/|| fallback chains; prefers DTOs, enums, generics, strict flags. Do NOT force typing onto untyped languages.

Convert a YouTube video transcript into a structured dossier: metadata, executive summary, timestamped key topics, notable quotes, takeaways, follow-ups. Trigger on: YouTube dossier, video to notes, transcript to summary, summarize YouTube video. Do NOT trigger for non-YouTube video, audio transcription, or downloading video files.

Codex CLI/App only passive delegation policy. Use in Codex when the user asks for subagents, delegation, parallel agents, one-agent-per-point reviews, multi-agent plans, or custom Codex agents. Spawn bounded subagents when useful; do NOT use outside Codex CLI/App, without explicit subagent/parallel-agent authorization, for trivial tasks, or as a fixed-model policy.

Audify readable URLs, Markdown, HTML, DOCX, or raw text into cleaned Gemini TTS MP3 narration. Trigger on /audify, read aloud, MP3 narration, or text-to-speech resource requests. Do NOT use for music, live voice chat, or non-narration media.

Draft local Azure DevOps work item packets from loose context, defaulting to Scrum PBI unless Bug, Feature, User Story, Task, Issue, or Epic is specified. Inspect repo context when present. Do NOT use for live REST/CLI creation, migration, wiki, or status reporting.

Write, fix, or review Azure DevOps wiki Markdown, Mermaid, _TOC_, _TOSP_, details blocks, query tables, mentions, work-item links, KaTeX, videos, and code fences. Use for Azure DevOps surface quirks. Do NOT use for GitHub-only or non-Azure docs.

Improve human-facing prose: docs, essays, explainers, PRs, memos, reports, newsletters, UI copy, and landing pages. Trigger on rewrite, make clearer, tighten, fix voice, or sharpen writing. Do NOT use for code-only work or factual verification without prose revision.

Turn git commits and diffs since an exact date into a copy-pastable, non-technical client report grouped by feature. Use for client updates, weekly progress, stakeholder recaps, or high-level git-history summaries. Do NOT use when the date is ambiguous.

Explain a codebase, subsystem, feature flow, or file cluster in clear accessible language. Trigger on how does this work, walkthrough, architecture explained simply, eli12, or mental model requests. Do NOT use for bug triage, code review, or code-change tasks.

Google-grounded SEO/GEO implementation for Search, AI Overviews, AI Mode, crawlability, indexability, snippets, structured data, ecommerce/local details, and agent browsing. Do NOT use for paid ads, rank tracking, non-Google directory tactics, or link schemes.

Convert repeated heuristics into deterministic behavior: validator scripts, normalizer tools, generators, fixtures, manifests, CI jobs, and hook-ready checks. Use to codify learnings and prevent future guessing. Do NOT use for pure brainstorming or one-off edits.