all publishers

canonical

@canonical source repo

99 published skills

  1. ▌
    Documentation Build 2 · canonical
    Validates documentation builds successfully. Use when checking Sphinx/RTD build integrity or diagnosing build failures. Reports errors, warnings, and build configuration issues.
    33 repo stars
  2. ▌
    Documentation Style 2 · canonical bundle
    Enforces project documentation style guide compliance for tone, voice, terminology, punctuation, and formatting. Use when checking documentation style or validating MyST/reST syntax. Cites specific style guide violations.
    33 repo stars
  3. ▌
    Documentation Review 2 · canonical bundle
    Performs comprehensive documentation review including build validation, Diataxis analysis, structure audit, accuracy verification, and style compliance. Use when reviewing documentation changes or auditing documentation quality.
    33 repo stars
  4. ▌
    Documentation Verify 2 · canonical bundle
    Verifies documentation accuracy by cross-referencing claims, CLI commands, API signatures, and configuration against source code. Use when validating documentation correctness or checking code-docs consistency. Flags unsupported or outdated claims.
    33 repo stars
  5. ▌
    Generate Agent 2 · canonical bundle
    Generates Custom Agent files (.github/agents/*.agent.md) with persona-based configurations, specialized tool sets, and role-specific cognitive architectures. Use when the user requests a specialized role or perspective (Security Auditor, Documentation Writer, Release Engineer, etc.). Creates agents with defined identity, constrained tools, and thinking processes aligned to their role. Not for general capabilities—use generate-agent-skills for those.
    33 repo stars
  6. ▌
    Documentation Diataxis 2 · canonical
    Analyzes documentation against Diataxis framework (Tutorial, How-to, Reference, Explanation). Use when reviewing documentation structure or classifying content type. Identifies misalignments between declared category and actual content.
    33 repo stars
  7. ▌
    Generate Prompt 2 · canonical bundle
    Generates reusable Prompt Template files (.github/prompts/*.prompt.md) with variable substitution for ad-hoc, high-frequency tasks. Use when the user needs quick, repeatable prompts for common operations (explain code, fix bug, add tests, refactor, document). Creates templates with handlebars variables, optimized context structure, and strict output constraints. Not for complex workflows (use skills) or persistent roles (use agents).
    33 repo stars
  8. ▌
    Documentation Structure 2 · canonical
    Validates documentation structural integrity including heading hierarchy, metadata, file naming, navigation, and cross-references. Use when checking documentation organization or validating toctree structure.
    33 repo stars
  9. ▌
    Generate Agent Skills 2 · canonical bundle
    Architects, generates, and validates Agent Skills. Enforces specification and best practices. Used any time an agent skill must be created or updated.
    33 repo stars
  10. ▌
    Generate Path Instructions 2 · canonical bundle
    Generates path-specific instruction files (.github/instructions/*.md) with JIT loading via applyTo glob patterns. Performs LLM-driven repository analysis to discover file patterns and extract scope-specific rules. Use when the user requests scoped, framework-specific, or directory-specific rules for testing, components, docs, config files, or language-specific files to prevent context pollution. Works for code, documentation, configuration, and data files.
    33 repo stars
  11. ▌
    Generate Repo Instructions 2 · canonical bundle
    Generates the global repository constitution file (.github/copilot-instructions.md). Works for code repositories, documentation repositories, data repositories, and mixed repos. Performs LLM-driven deep repository analysis including docs, code patterns, build systems, documentation generators, and data schemas. Generates constitutional rules following context economics (under 1000 lines). Enforces positive constraints and no hardcoded secrets.
    33 repo stars
  12. ▌
    Svelte Core Bestpractices · canonical bundle
    Guidance on writing fast, robust, modern Svelte code. Load this skill whenever in a Svelte project and asked to write/edit or analyze a Svelte component or module. Covers reactivity, event handling, styling, integration with libraries and more.
    33 repo stars
  13. ▌
    Test Writer · canonical bundle
    Use whenever you need to write a unit, integration or component test.
    33 repo stars
  14. ▌
    Deep Modules · canonical bundle
    Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
    33 repo stars
  15. ▌
    Plan Feature · canonical
    Use when the user wants a plan or breakdown for building a feature (or significantly reshaping one) before any code is written. Turns a feature request into a written implementation plan of self-contained, independently testable vertical slices. Do NOT use for bugfixes, refactors with no behavior change, or trivial one-step tasks.
    33 repo stars
  16. ▌
    Code Reviewer · canonical
    Use when reviewing code changes. Checks Svelte 5 runes usage, SvelteKit data-loading/endpoints, server-only and env/secret boundaries, SSR state leakage, storefront pitfalls (money, cart/price/stock trust boundaries, payments, SEO, a11y, caching), tests, and the repo's verification gates. Use ONLY for reviewing/critiquing existing code, not for writing new features.
    33 repo stars
  17. ▌
    Document Feature · canonical
    Use when the user asks for documentation. Use when a new feature has been built or significantly changed and its design/decisions should be recorded in the repo's docs/. Captures the approach (and optional rationale) into per-topic markdown files (testing, api-endpoints, routes, data-loading, components, state-management, business-logic, forms-actions, auth, error-handling, build-deployment). Do NOT use for bugfixes, style tweaks, or other small tasks.
    33 repo stars
  18. ▌
    Figma Context · canonical
    Pulls design context from Figma via the Figma desktop MCP server during documentation workflows. Use when a user provides a Figma URL, selects a node in the Figma desktop app, or references existing designs during discovery, drafting, or review.
    33 repo stars
  19. ▌
    Brand Voice Evaluation · canonical
    Evaluates documentation against the team's brand guidelines. Use when reviewing docs for tone, terminology, sentence structure, and phrasing consistency.
    33 repo stars
  20. ▌
    Readability Evaluation · canonical bundle
    Scores and evaluates documentation readability using Flesch-Kincaid metrics and qualitative analysis. Use when reviewing docs for sentence length, passive voice, jargon, and reading level.
    33 repo stars
  21. ▌
    Completeness Evaluation · canonical
    Evaluates whether documentation sections have substantive content. Use when checking whether planned sections are complete, thin, placeholders, or missing.
    33 repo stars
  22. ▌
    Copy Editing Evaluation · canonical bundle
    Evaluates grammar, spelling, and formatting in design systems' documentation. Use when checking mechanics like spelling, punctuation, heading hierarchy, and list formatting.
    33 repo stars
  23. ▌
    Explore Existing Ds Docs · canonical bundle
    Explore Canonical's Vanilla Framework design system documentation. Covers 49 UI constructs and 26 concepts including their properties, anatomy, usage guidelines, and relationships. Use when answering questions about Vanilla constructs, concepts, design patterns, or implementation details.
    33 repo stars
  24. ▌
    Lxd · canonical bundle
    Workflows for LXD containers and VMs: launch Ubuntu instances, mount host directories and storage volumes, and define reusable profiles and networks.
    33 repo stars
  25. ▌
    Reviewskill · canonical bundle
    Prepare and perform deterministic all-rubric code reviews for working-tree changes, branch/range diffs, GitHub pull requests, or complete repositories. Use when the user asks for a code review.
    33 repo stars
  26. ▌
    Diagnose Sunbeam · canonical
    Use when diagnosing failed Sunbeam CI runs, analyzing sosreport tarballs, juju status files, sunbeam CLI logs, or investigating multi-node OpenStack deployment failures on Canonical K8s
    33 repo stars
  27. ▌
    Plot Fio Results · canonical bundle
    Generate a 4-panel matplotlib chart from rally-ci-churn fio benchmark result files. Use when you have result files in the results/ directory and want to visualize throughput scaling, IOPS, latency (avg/P99), and scaling efficiency. Triggers: plot results, chart fio, visualize benchmark, fio chart, throughput chart.
    33 repo stars
  28. ▌
    Sunbeam Networking · canonical bundle
    Sunbeam/OpenStack lab networking knowledge for new joiners. Use when: explaining NICs, bonds, fabrics, VLANs, switches, routers, bridges; configuring MAAS interfaces for a new node; debugging missing Juju spaces; onboarding to the Sunbeam lab network; creating network diagrams or PPTs; understanding why a charm deployment fails due to network bindings. Covers: lab rack layout, management-fabric vs data-fabric, bondm/bondd/bond2/br-bond2 structure, VLAN IDs 3400-3409, Juju space to subnet mapping, step-by-step MAAS CLI commands.
    33 repo stars
  29. ▌
    Cinder Spec Generator · canonical bundle
    Extracts oslo.config options from OpenStack Cinder volume driver Python source code and generates driver-spec YAML files for sunbeam-cinder-factory. Use when adding new storage vendor support, updating existing driver specs from upstream Cinder, or batch-generating specs for all Cinder drivers. Handles AST parsing, type classification, secret detection, protocol detection, enum mapping, and type_override generation.
    33 repo stars
  30. ▌
    Setup Charm Monorepo · canonical
    Set up a charm monorepo with a scripts/repository.py CLI tool and a UHPC011-compliant justfile. Use when scaffolding or reviewing a monorepo repository that uses uv workspaces, repository.py for tooling, and just as the developer entry point.
    33 repo stars
  31. ▌
    Jubilant Bdd Migration · canonical bundle
    Migrate an existing Juju charm repo's pytest integration tests to Behavior-Driven Development (BDD) by authoring YAML test plans with gherkinator that generate Gherkin feature files backed by pytest-jubilant-bdd's reusable step handlers. Use when asked to "migrate tests to BDD", "convert to Gherkin", "use pytest-jubilant-bdd", or to Gherkin-ize jubilant-based integration tests in a charm repo (e.g. slurm-charms, filesystem-charms, sssd-operator). Do NOT use for the pytest-jubilant-bdd plugin's own unit tests.
    33 repo stars
  32. ▌
    Migrate Charm To 26 04 · canonical
    Migrate a Juju charm (or monorepo of charms) from an Ubuntu 24.04 base to the Ubuntu 26.04 (Resolute) base. Use this when the user wants to upgrade a charm's charmcraft.yaml base, Python version, CI workflows, test dependencies, and documentation, and verify the juju snap/controller versions required for 26.04.
    33 repo stars
  33. ▌
    Create Juju Integration Interface Readme · canonical
    Create README files for standalone Juju integration interface implementation packages and libraries. Use when writing, reviewing, or generating a README for an interface library package that implements a provider/requirer pattern for Juju charm relations.
    33 repo stars
  34. ▌
    Create Charmed Hpc Justfile · canonical
    Create or review justfiles for Charmed HPC repositories following the UHPC011 Common justfile format specification. Use when writing, validating, or restructuring a justfile that must conform to the Charmed HPC standard.
    33 repo stars
  35. ▌
    Update Agents Skills Readme · canonical
    Update the README.md in .agents/skills/ when agent skills are added, removed, or modified. Use when the set of skills under .agents/skills/ changes and the README must be regenerated to reflect the current state.
    33 repo stars
  36. ▌
    Create Charm Terraform Module · canonical
    Create or review Terraform modules for individual Juju charms following the CC008 Charm Terraform Standards specification. Use when writing, validating, or restructuring a charm-level Terraform module that uses the Terraform Juju provider.
    33 repo stars
  37. ▌
    Documentation Build · canonical
    Validates documentation builds successfully. Use when checking Sphinx/RTD build integrity or diagnosing build failures. Reports errors, warnings, and build configuration issues.
    33 repo stars
  38. ▌
    Documentation Style · canonical bundle
    Enforces project documentation style guide compliance for tone, voice, terminology, punctuation, and formatting. Use when checking documentation style or validating MyST/reST syntax. Cites specific style guide violations.
    33 repo stars
  39. ▌
    Documentation Review · canonical bundle
    Performs comprehensive documentation review including build validation, Diataxis analysis, structure audit, accuracy verification, and style compliance. Use when reviewing documentation changes or auditing documentation quality.
    33 repo stars
  40. ▌
    Documentation Verify · canonical bundle
    Verifies documentation accuracy by cross-referencing claims, CLI commands, API signatures, and configuration against source code. Use when validating documentation correctness or checking code-docs consistency. Flags unsupported or outdated claims.
    33 repo stars
  41. ▌
    Documentation Diataxis · canonical
    Analyzes documentation against Diataxis framework (Tutorial, How-to, Reference, Explanation). Use when reviewing documentation structure or classifying content type. Identifies misalignments between declared category and actual content.
    33 repo stars
  42. ▌
    Documentation Structure · canonical
    Validates documentation structural integrity including heading hierarchy, metadata, file naming, navigation, and cross-references. Use when checking documentation organization or validating toctree structure.
    33 repo stars
  43. ▌
    Docs AI Friendly Rewrite · canonical bundle
    Rewrite existing documentation so LLMs can reason and infer from it, not just retrieve matching snippets. Use whenever asked to make docs "AI-friendly," "LLM-friendly," or "inference-friendly," to answer questions the docs don't state verbatim, or to audit/rewrite documentation for AI consumption. Applies to this repo's Sphinx/MyST/RST Diátaxis content under docs/.
    33 repo stars
  44. ▌
    Review Pr · canonical
    Review a pull request, address inline reviewer comments, post replies, and apply fixes. Use when asked to review PR feedback, respond to comments, or fix issues raised in a PR.
    33 repo stars
  45. ▌
    Setup K8S · canonical
    Set up Canonical k8s and register it as a Juju cloud inside the sandbox VM. Use when asked to set up a k8s substrate, prepare for Kubernetes charm deployments, or before bootstrapping a Juju k8s controller.
    33 repo stars
  46. ▌
    Setup Lxd · canonical
    Set up LXD and register it as a Juju cloud inside the sandbox VM. Use when asked to set up an LXD substrate, prepare for machine charm deployments, or before bootstrapping a Juju LXD controller.
    33 repo stars
  47. ▌
    File Issue · canonical
    File a GitHub issue (bug report or enhancement proposal) on any repository, not just canonical/charm-integration-testing. Use when asked to open, file, or create an issue for a bug, failure, or enhancement idea, whether in this repo or another one (e.g. an upstream charm repo).
    33 repo stars
  48. ▌
    Test Validator · canonical
    Test an existing Juju charm integration validator against a deployed charm. Use when asked to test, verify, or run an existing validator.
    33 repo stars
  49. ▌
    Run Charm Tests · canonical
    Run charm integration tests to reproduce test failures and issues. Uses scripts/run-tests.sh with test observer parameters to recreate exact test scenarios locally.
    33 repo stars
  50. ▌
    Develop Validator · canonical
    Develop a new Juju charm integration validator from scratch. Use when asked to create, write, or build a new validator for an interface.
    33 repo stars
  51. ▌
    Setup Charm Tests · canonical
    Install charm testing prerequisites - cloud substrates and logging tools. The test suite handles controller bootstrap.
    33 repo stars
  52. ▌
    Charm Override Investigator · canonical
    Charm Override Investigator - investigates charm metadata and creates per-charm override YAML files in static/charm-overrides/. USE FOR: creating a new override from scratch, updating after an upstream PR lands, fixing broken constraints, auditing against live metadata, recording expected resource inconsistencies (e.g. a retained PVC) so the resource tracker does not flag them. GUIDED WORKFLOWS: write_new_override, update_existing_override, validate_override, write_resource_inconsistency_override. INPUTS: charm name, optional upstream PR URL, optional track filter. OUTPUTS: PR-ready YAML with evidence comments.
    33 repo stars
  53. ▌
    Agents Md · canonical
    This skill should be used when the user asks to "create AGENTS.md", "update AGENTS.md", "maintain agent docs", "set up CLAUDE.md", or needs to keep agent instructions concise. Enforces research-backed best practices for minimal, high-signal agent documentation.
    33 repo stars
  54. ▌
    Skill Writer · canonical bundle
    Author, structure, and validate an agent skill. Use when creating a new SKILL.md, substantially rewriting an existing one, deciding what to bundle as scripts vs references, or importing an external skill. Covers frontmatter, body structure, depth gates (when to split a skill), the script-vs-checklist decision, prompt-injection hygiene, validation, and testing.
    33 repo stars
  55. ▌
    Skill Scanner · canonical bundle
    Scan an agent skill for security and quality issues. Use when asked to "scan a skill", "audit a skill", "review skill security", "check a skill for prompt injection", "validate SKILL.md", or assess whether a skill is safe to install. Checks for prompt injection, scope bloat, description drift, malicious scripts, secret exposure, excessive permissions, and supply-chain risk.
    33 repo stars
  56. ▌
    Iterate Pr · canonical bundle
    Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automates the feedback-fix-push-wait cycle.
    33 repo stars
  57. ▌
    Go Standards · canonical bundle
    Canonical Go coding standards and best practices. Use when writing, reviewing, or refactoring Go code. Covers formatting, naming, errors, functions, structs, interfaces, and testing conventions.
    33 repo stars
  58. ▌
    CLI Standards · canonical bundle
    Canonical CLI design standards. Use when designing, implementing, or reviewing command-line interfaces. Covers grammar, commands, flags, parameters, feedback, colours, tables, verbosity, and tone of voice.
    33 repo stars
  59. ▌
    Ct Code Review · canonical
    Canonical code review guidelines. Use when reviewing code, preparing PRs for review, or giving feedback on changesets. Covers tone, procedures, code quality, changeset scope, and review process.
    33 repo stars
  60. ▌
    Ct Security Review · canonical bundle
    Security code review for vulnerabilities. Use when asked to "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP review", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting.
    33 repo stars
  61. ▌
    Gha Security Review · canonical bundle
    GitHub Actions security review for workflow exploitation vulnerabilities. Use when asked to "review GitHub Actions", "audit workflows", "check CI security", "GHA security", "workflow security review", or review .github/workflows/ for pwn requests, expression injection, credential theft, and supply chain attacks. Exploitation-focused with concrete PoC scenarios.
    33 repo stars
  62. ▌
    Add Standard · canonical
    Create and add a new code standard to the code-standards package
    33 repo stars
  63. ▌
    Anatomy Author · canonical bundle
    Write component anatomy specifications using the Design System Anatomy DSL; also runs as a guided tutorial on a worked example
    33 repo stars
  64. ▌
    Design Auditor · canonical
    Audit design system coverage, consistency, and quality; also runs as a guided tutorial on a worked example
    33 repo stars
  65. ▌
    Specify Pattern · canonical
    Specify a new design-system pattern from the repeatable user context it serves; also runs as a guided tutorial on a worked example
    33 repo stars
  66. ▌
    Adoption A3 Forms · canonical
    Migrate application forms to the Canonical form system built on react-hook-form (adoption track A3); also runs as a guided tutorial on a worked example
    33 repo stars
  67. ▌
    Specify Component · canonical
    Specify a new design-system component with the knowledge graph, from graph search to a sync-safe spec file; also runs as a guided tutorial on a worked example
    33 repo stars
  68. ▌
    Adoption A1 Styles · canonical
    Adopt Canonical design-system styles, fonts, and icons in an application (adoption track A1); also runs as a guided tutorial on a worked example
    33 repo stars
  69. ▌
    Implement Component · canonical
    Implement a specified design-system component with pragma create, following the live code standards; also runs as a guided tutorial on a worked example
    33 repo stars
  70. ▌
    Adoption A2 Components · canonical
    Swap an application's UI to Canonical design-system components one component type per PR (adoption track A2); also runs as a guided tutorial on a worked example
    33 repo stars
  71. ▌
    Sl Internal · canonical bundle
    The Squeeze Loop (SL) strategy
    33 repo stars
  72. ▌
    Polish Skill · canonical
    Polish Skill
    33 repo stars
  73. ▌
    Write A Paper · canonical
    A general-purpose academic-paper-writing companion that encodes hard-won lessons (many from reviewer feedback) for writing a clear, honest, and defensible paper. Covers saying each idea once, resolving forward references, connective tissue, avoiding overclaim, citing responsibly, tightening the abstract, keeping front matter in sync with the body, cross-section consistency, bounding speculative material, quantifying honestly, figures, length discipline, and independent editorial review. Use whenever the user says "help me write a paper", "review my paper draft for clarity", "is my abstract overclaiming", "academic writing help", "polish my manuscript", "did I make a forward reference", "say it once", "check my paper for consistency", "read the full paper for consistency", "make sure each term is defined / introduced before use", "run a summary-vs-body faithfulness sweep", "make this qualifier/term consistent everywhere", "is this claim defensible", "how should I cite this", "did I leave stale future-work lang
    33 repo stars
  74. ▌
    Sl Monitoring Sl · canonical bundle
    Specifies how one squeeze loop monitors another squeeze loop — squeezing the monitored loop's soft outputs (especially its accumulated skills / learned heuristics) against that loop's own upper and lower bounds, from an independent evidence base; it classifies a skill by kind (ignore-signal vs defer-to-oracle), runs the matching consistency check, and repairs by carving over-generalized skills with bound-deferring exceptions or pruning spurious ones. Use when a loop accumulates or consolidates skills that may over-reach; when you need a meta-loop or monitor that audits a base loop's learned rules for contradictions with its spec; when a learned heuristic seems to conflict with the governing policy; or when reasoning about the "disjointness principle applied to skills." Trigger phrasings include "a loop monitoring a loop", "monitor the squeeze loop", "check a skill against the upper bound", "the skill contradicts the spec", "carve out an exception", "prune a spurious skill", "who audits the learned skill", "sk
    33 repo stars
  75. ▌
    Use Case A · canonical
    Use Case A — the metric-handbook squeeze loop
    33 repo stars
  76. ▌
    Use Case B · canonical
    Use Case B — the authored-authority refund-bot squeeze loop
    33 repo stars
  77. ▌
    Use Case C · canonical
    Use Case C — the split-planes API squeeze loop
    33 repo stars
  78. ▌
    Use Case D · canonical
    Use Case D — the deductive-kernel proof squeeze loop
    33 repo stars
  79. ▌
    Use Case Paper · canonical
    Use Case Paper — the reflexive instance (a monitor over A–D)
    33 repo stars
  80. ▌
    Rocq · canonical bundle
    Guide Rocq/Coq theorem proving, proof debugging, library search, and formalization. Use when editing .v files, debugging Rocq/Coq builds (type mismatch, Admitted, failed to unify, axiom warnings, coqc errors), searching for lemmas in stdlib or MathComp, formalizing mathematics in Rocq, or learning Rocq concepts. Also trigger when the user asks for help with Rocq, Coq, MathComp, or _CoqProject. Do NOT trigger for Lean 4, Agda, Isabelle, HOL4, Mizar, Idris, Megalodon, or other non-Rocq theorem provers.
    33 repo stars
  81. ▌
    Sl Auditor · canonical bundle
    Audits an existing Squeeze Loop (SL) for soundness — checking whether a target loop is truly compliant (pairwise-disjoint authority pairs, physically barriered contexts, gate-defined "done", a genuine executable lower bound, and demonstrated catching of coherent-and-wrong) or is quietly collapsing into a rubber stamp. It applies the squeeze's own discipline to the loop under audit: it maps the actual (upper, lower) authority pairs and hunts for an actor certifying its own work; probes whether each context barrier is physical or merely honorary; confirms an executable oracle disjoint from the actor it judges; checks Gate A / Gate B / Gate C are present and load-bearing; seeds coherent-and-wrong artifacts to calibrate the monitors (flag rate not zero, not saturated); audits the loop's accumulated learned skills VIA the sl-monitoring-sl pattern; checks each known collapse mode is blocked by a stabilizer; and routes whatever an internal audit cannot self-certify to a disjoint base (external / cross-provider / hum
    33 repo stars
  82. ▌
    Sl Builder · canonical
    Interview a human who wants to build a Squeeze Loop (SL) for their problem, then draft a concrete, structured plan. Elicits the deliverable, the upper bound (soft normative authority — spec/standard/policy/contracts), the lower bound (executable oracle — prover/checker/tests/runtime/reference impl), the actors and their disjoint (U,L) pairs, the context barriers, the gates (A editorial / B machine / C coverage-no-blend), the coherent-and-wrong failure to guard, and the stabilizers/collapse modes to pre-empt — then turns the answers into a roles+bounds+barriers+gates+loop-steps plan. Use when the user says any of: "draft a plan to generate a squeeze loop", "draft an SL validation plan", "build an SL strategy for X", "design a squeeze loop for my problem", "help me set up a squeeze loop", "SL validation plan for C code with Frama-C", "an SL that monitors another SL", "nested squeeze loop / monitor of a monitor". Action-oriented: figure out what is known, ASK the missing interview questions, then OUTPUT a plan i
    33 repo stars
  83. ▌
    Secret Guard · canonical bundle
    Lets an agent authenticate to APIs and MCP servers WITHOUT ever seeing secret values. Use whenever a task needs an API token, MCP token, password, or key. The agent passes a credential *reference* (a name); a trusted non-LLM broker resolves it from the OS keyring, injects it into the request, scrubs the response, and returns only scrubbed output. The secret value never enters the agent's context or the LLM.
    33 repo stars
  84. ▌
    Generate Agent · canonical bundle
    Generates Custom Agent files (.github/agents/*.agent.md) with persona-based configurations, specialized tool sets, and role-specific cognitive architectures. Use when the user requests a specialized role or perspective (Security Auditor, Documentation Writer, Release Engineer, etc.). Creates agents with defined identity, constrained tools, and thinking processes aligned to their role. Not for general capabilities—use generate-agent-skills for those.
    33 repo stars
  85. ▌
    Generate Prompt · canonical bundle
    Generates reusable Prompt Template files (.github/prompts/*.prompt.md) with variable substitution for ad-hoc, high-frequency tasks. Use when the user needs quick, repeatable prompts for common operations (explain code, fix bug, add tests, refactor, document). Creates templates with handlebars variables, optimized context structure, and strict output constraints. Not for complex workflows (use skills) or persistent roles (use agents).
    33 repo stars
  86. ▌
    Changelog Generator · canonical
    Generates structured changelogs from git history and pull requests. Use when preparing release notes, summarizing changes between tags/branches, or maintaining a CHANGELOG.md file. Supports Conventional Commits parsing.
    33 repo stars
  87. ▌
    Generate Agent Skills · canonical bundle
    Architects, generates, and validates Agent Skills. Enforces specification and best practices. Used any time an agent skill must be created or updated.
    33 repo stars
  88. ▌
    Retrospective Artifacts · canonical bundle
    Builds and parses structured retrospective artifact folders for troubleshooting, incident review, and delivery retros. Use this skill when capturing session context, synthesizing external context (GitHub, Jira, Mattermost, logs), querying prior retrospectives, or preparing downstream inputs for OKB entries, postmortems, and agent/skills/instruction improvements.
    33 repo stars
  89. ▌
    Generate Path Instructions · canonical bundle
    Generates path-specific instruction files (.github/instructions/*.md) with JIT loading via applyTo glob patterns. Performs LLM-driven repository analysis to discover file patterns and extract scope-specific rules. Use when the user requests scoped, framework-specific, or directory-specific rules for testing, components, docs, config files, or language-specific files to prevent context pollution. Works for code, documentation, configuration, and data files.
    33 repo stars
  90. ▌
    Generate Repo Instructions · canonical bundle
    Generates the global repository constitution file (.github/copilot-instructions.md). Works for code repositories, documentation repositories, data repositories, and mixed repos. Performs LLM-driven deep repository analysis including docs, code patterns, build systems, documentation generators, and data schemas. Generates constitutional rules following context economics (under 1000 lines). Enforces positive constraints and no hardcoded secrets.
    33 repo stars
  91. ▌
    Landscape Jira · canonical
    Creates well-formed Jira issues in the LNDENG project (warthogs.atlassian.net) — stories, epics, objectives, tasks, spikes, bugs, and more — with correct field mappings, sprint assignment, and acceptance criteria.
    33 repo stars
  92. ▌
    Ubuntu Write Sru · canonical
    Generates a complete Ubuntu SRU Bug Description template ([Impact], [Test Plan], [Where problems could occur]) using interactive human guidance to filter out noise. Trigger phrases: "sru template", "ubuntu sru description", "write sru bug".
    33 repo stars
  93. ▌
    Ubuntu Review Ffe · canonical bundle
    Review an Ubuntu Feature Freeze exception (FFe) request filed as a Launchpad bug for compliance with the Release Team process, and produce a report with a recommendation.
    33 repo stars
  94. ▌
    Ubuntu Review New · canonical bundle
    Validates and reviews an Ubuntu package in the NEW queue, merge request, bug, or PPA for compliance with Ubuntu and Debian NEW rules before sponsoring or acceptance.
    33 repo stars
  95. ▌
    Ubuntu Review Sru · canonical bundle
    Review an Ubuntu Stable Release Update (SRU) and produce a report with a recommendation.
    33 repo stars
  96. ▌
    Ubuntu Review Uife · canonical bundle
    Review an Ubuntu UI Freeze exception (UIFe) request filed as a Launchpad bug for compliance with the Release Team process, and produce a report with a recommendation.
    33 repo stars
  97. ▌
    Migrate Harness Tests To State Transition Test · canonical bundle
    Migrates legacy ops.testing Harness suites to state-transition tests by enumerating Harness usages, defining explicit State objects, and recreating assertions per Juju event so charms stay compatible with modern ops releases.
    33 repo stars
  98. ▌
    Ubuntu Create Autopkgtest · canonical
    Author or improve debian/tests/ for as-installed Debian/Ubuntu package testing per DEP-8. Detects package shape (library, daemon, CLI tool, data), proposes the minimal Restrictions set, and produces a draft debian/tests/control plus test scripts for the maintainer to run. Advisory only — does not run tests.
    33 repo stars
  99. ▌
    Ubuntu Review Final Freeze · canonical bundle
    Review an Ubuntu Final Freeze exception request filed as a Launchpad bug for compliance with the Release Team process, and produce a report with a recommendation.
    33 repo stars