pantheon-org
- 176 skills
- 0 followers
- 6 hours ago last updated
- ▌ Code Quality Advisor · pantheon-orgEvaluates code quality across a range of dimensions including readability, maintainability, and structural coherence. Provides actionable feedback to help developers improve their codebase through targeted suggestions and best practice guidance.
- ▌ Pr Style Checker · pantheon-orgAnalyzes pull request diffs and detects style issues in each commit. Does not apply to auto-generated migration files or vendored dependencies. Use before merging to catch regressions early in your pipeline config.
- ▌ Pr Author · pantheon-org bundleCreate and maintain GitHub PRs with live descriptions — template discovery, intelligent filling, and lifecycle updates. Triggers on: PR, pull request, create PR, update PR description, draft PR, open PR, format PR, PR template, change request, re-request review, review feedback, force-push PR, PR ready for review.
- ▌ Docs Check · pantheon-org bundleValidate the GitHub Pages documentation site built by @docmd/core. Covers build verification, orphan detection, ADR index freshness, cross-reference integrity, and LLM output audit. Use when editing docs, after merging doc changes, before deploying, or when troubleshooting a broken site build. Do NOT use for content quality review (use markdown-authoring) or agent skill documentation review (use skill-quality-auditor). Triggers: 'check docs', 'build docs', 'verify site', 'docs audit', 'orphan detection', 'docmd check', 'preview docs', 'LLM output check', 'ADR index check', 'documentation validation'.
- ▌ Adr Capture · pantheon-org bundleCapture Architecture Decision Records (ADRs) from .context/ plans, findings, and analyses. Extracts binding decisions into numbered ADRs under docs/ADR/, maintains a machine-readable index, and validates coverage. Use when creating or reviewing context files that contain decisions. DO NOT use for observational findings without decisions, retroactive documentation of long-settled decisions, or inline comments. Triggers: 'capture decision', 'create ADR', 'document decision', 'architectural decision', 'record decision as ADR', 'extract decisions', 'ADR review', 'index ADRs', 'check ADR coverage'.
- ▌ Design Debate · pantheon-org bundleStress-test an unwritten idea or decision by spawning independent subagents in genuinely OPPOSING roles (advocate, skeptic, migration/risk) rather than complementary review lenses — grounded in real repo investigation, not assumption, and concluding in a synthesized verdict rather than a list of opinions. Use for "should we do X", "what are the pros and cons", "I need pushback", "collegial review", "second opinion on this decision" — BEFORE a plan exists. NOT for reviewing an already-written plan file (use plan-review) and NOT for refining a vague question through dialogue with the user (use socratic-method).
- ▌ Context File · pantheon-org bundleCreate a new .context/ file (plan, finding, or analysis) with standard YAML frontmatter. Use when documenting a decision, writing an implementation plan, recording research findings, or capturing analysis output. DO NOT use for ephemeral notes, secrets storage, or skill remediation plans (use skill-auditor remediate instead). Triggers: 'create a plan', 'new finding', 'document this', 'write analysis', 'new context file', 'capture findings', 'draft a plan', 'record decision'.
- ▌ External Source Fit · pantheon-org bundleAssess whether an external GitHub repo, file, project fits the skill-quality-auditor project: what it actually is (not what its name implies); whether it overlaps existing capability (D1-D9 scorers, validate, duplication, eval runner, helper skills); whether it belongs in the Go CLI versus a helper skill; what is worth learning from even a rejected source; whether the project needs it. Ends by writing a house-standard FINDING, flagging any binding decision for ADR capture. Use when someone links an external repo, file, project asking whether it fits, whether we can learn from it, whether we need it. Do NOT use for reviewing internal code (use review-changes), scoring a SKILL.md (use skill-quality-auditor), doing web research (use deep-research). Triggers: 'does this repo fit', 'evaluate this project', 'assess this external repo', 'would this fit our project', 'can we learn from', 'is this worth adopting', 'fit assessment', 'should we import', 'should we port this'.
- ▌ Pin · pantheon-org bundlePin session decisions, questions, objections, scope constraints, and corrections to a persistent board that survives context compaction. Use PROACTIVELY when: (1) user approves/rejects a recommendation, (2) user asks a clarifying question about a proposal, (3) user states a scope constraint, (4) user corrects a misunderstanding. Also use when user says pin, track this, mark as approved, board, show pins. Auto-invoke without user asking whenever a decision, question, or constraint is detected.
- ▌ Bdd Testing · pantheon-org bundleWrite and maintain Behavior-Driven Development tests with Gherkin and Cucumber. Use when defining acceptance scenarios, writing feature files, implementing step definitions, running Three Amigos sessions, or diagnosing BDD test quality issues. Keywords: bdd, gherkin, cucumber, given when then, feature files, step definitions, acceptance criteria, three amigos, example mapping.
- ▌ Helm Generator · pantheon-org bundleComprehensive toolkit for generating best practice Helm charts and resources following current standards and conventions. Use this skill when creating new Helm charts, implementing Helm templates, scaffolding Chart.yaml and values.yaml, defining deployment templates, service definitions, ingress configurations, .tpl helpers, or building Helm projects from scratch. Trigger phrases include "create", "generate", "build", "scaffold" alongside terms like "kubernetes helm", "k8s charts", "helm package", "chart dependencies", "values.yaml", or "helm install".
- ▌ Helm Validator · pantheon-org bundleComprehensive toolkit for validating, linting, testing, and analyzing Helm charts and their rendered Kubernetes resources. Use this skill when working with Helm charts, validating templates, debugging chart issues, working with Custom Resource Definitions (CRDs) that require documentation lookup, or checking Helm best practices.
- ▌ Follow Up · pantheon-org bundleRead-only status check across the follow-up backlog: lists every ACTIVE follow-up entry, assesses whether it's still genuinely open, and recommends the single best next item to work on -- pulling in open RISK_REGISTER and TECH_DEBT rows and the value-rubric's ranked PLAN/FINDING/KNOWN_ISSUE candidates when the follow-up list itself is empty, since that's where promoted follow-up work actually ends up living. Triggers: '/follow-up', 'check follow-ups', 'what's open', 'what should I work on next', 'follow-up status check', 'next best item', 'what's still open'. Does NOT promote, close, or otherwise edit anything -- it reports and recommends, then applies follow-up-triage's own flow directly or hands off to the risk-register / tech-debt / plan-create skills for the actual write.
- ▌ Tech Debt · pantheon-org bundleMaintain docs/TECH_DEBT.md, the living list of code-level cleanup that isn't a risk, a shortcut, or an open decision (that's the risk-register skill's job) and isn't a future feature (that's ROADMAP.md's job). Use when a lint/format/style violation slips past an existing gate, a small known cleanup is noticed while working on something else, or a filed item is fixed and needs removing. DO NOT use for anything with a real cost or risk if left unaddressed (use risk-register instead), for aislop baseline findings (already lifecycle-managed in .aislop/baseline.json), or for anything confidential. Triggers: 'add to tech debt', 'log this as cleanup', 'track this lint violation', 'mark tech-debt item #N fixed', 'what's on the tech debt list'.
- ▌ Gitlab API · pantheon-org bundleFetches and analyzes GitLab merge request (MR) comments, metadata, and review feedback using authenticated API calls. Capabilities include fetching comment threads, retrieving reviewer feedback, filtering unresolved discussions, and generating MR activity reports. Use when the user asks about GitLab MR comments, code review discussions, review feedback, approval status, troubleshooting review delays, or needs to fetch merge request metadata via the GitLab API.
- ▌ Commanderjs · pantheon-org bundleComplete Commander.js CLI framework guidance covering command structure, options, arguments, subcommands, action handlers, version management, and TypeScript integration. Use when: building CLI tools, parsing command-line arguments, implementing subcommands, handling options/flags, creating interactive CLIs, or migrating from other CLI frameworks. Keywords: Commander.js, CLI, command-line, arguments, options, flags, subcommands, action handlers, version, help text, TypeScript, yargs, meow, program, parseAsync, opts, args, variadic, required options, default values, custom help, error handling
- ▌ Humanizer · pantheon-org bundleRemove 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
- ▌ Clarke Dawe Esque · pantheon-org bundleWrite an original deadpan two-person political-satire interview sketch (a mock-interview bit, not a monologue, panel show, or sitcom scene) using terse questions, absolutely-confident literal-minded answers, repetition, bureaucratic logic, and escalating contradiction, in the tradition of John Clarke and Bryan Dawe's satirical news interviews. Use this when a user asks for a satirical interview, mock-interview sketch, deadpan two-hander, or "Clarke and Dawe style" bit built around a policy, institution, or current-events topic. Do NOT use this for stand-up monologue jokes, sketch comedy with more than two speaking roles, sitcom-style scenes with stage direction and physical comedy, or any request to reproduce an actual historical Clarke and Dawe transcript verbatim — this skill generates new satire, it does not retrieve or reconstruct existing scripts.
- ▌ K8S Debug · pantheon-org bundleInspect pod logs, analyze resource quotas, trace network policies, check deployment rollout status, and run cluster health checks for Kubernetes. Use this skill when diagnosing Kubernetes cluster issues, debugging failing pods, investigating network connectivity problems, analyzing resource usage, troubleshooting deployments, or performing cluster health checks.
- ▌ Plan Create · pantheon-org bundleCreate `.context/plans/*.md` files with standard YAML frontmatter, phases/tasks/waves decomposition, and post-creation validation. Infers section conventions from existing plans in `.context/plans/` to match the local style. Integrates with plan-review for a create → review → iterate loop. Triggers: 'create a plan', 'new plan', 'draft a plan', 'plan scaffold', 'write a plan'. Do NOT use for plans outside `.context/plans/`, ephemeral notes, or the main project SKILL.md.
- ▌ Plan Review · pantheon-org bundleReview .context/plans/*.md files using 3 independent subagent reviewers: Technical (feasibility, gaps, soundness), Strategic (scope, alignment, priority), and Risk (blind spots, edge cases, failure modes). The skill FIRST asks the user which models to assign to each reviewer -- presenting available options based on the user's environment (OpenCode Zen, OpenCode Go, a native Anthropic CLI harness, or BYOK). Each reviewer receives the same plan with a role-specific lens and returns structured feedback. The main agent consolidates all three perspectives. Triggers: 'review this plan', 'audit plan', 'plan review', 'check my plan', 'what's wrong with this plan', 'review all plans', 'plan quality check'. Do NOT use for plans not in .context/plans/, one-off notes, or external documents.
- ▌ How · pantheon-org bundleUse for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Can critique architecture. DO NOT use for design rationale or history (use why instead), or for proving a change is safe to ship (use blast-radius instead). Triggers: how does X work, walk me through X, where should this live, critique this architecture, whats wrong with this design.
- ▌ Why · pantheon-org bundleUse for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. DO NOT use for explaining current runtime behavior (use how instead), or for proving a change is safe to ship (use blast-radius instead). Triggers: why does X work this way, why did we pick Y over Z, what motivated this, why does this still exist, history of X.
- ▌ Agents Md · pantheon-org bundleCreate and maintain AGENTS.md documentation for simple projects, complex monorepos, deterministic discovery, scoped instruction files, low-token navigation; use when generating AGENTS.md, updating agent docs, standardizing AI-facing project guidance.
- ▌ Fluentbit Generator · pantheon-org bundleGenerates, validates, and optimizes Fluent Bit configurations for production use. Use when creating new Fluent Bit configs, implementing log collection pipelines (INPUT, FILTER, OUTPUT sections), configuring Kubernetes log collection with metadata enrichment, forwarding logs to destinations (Elasticsearch, Loki, S3, Kafka, CloudWatch, OpenTelemetry), building multi-line log parsing, or converting existing logging configurations to Fluent Bit.
- ▌ Fluentbit Validator · pantheon-org bundleValidates syntax, checks pipeline tag connections, detects security misconfigurations, audits best practices, and performs dry-run testing for Fluent Bit configurations. Use this skill when working with Fluent Bit config files, validating syntax, checking for best practices, identifying security issues, performing dry-run testing, or troubleshooting configuration-related errors.
- ▌ Gitlab CI Generator · pantheon-org bundleCreates .gitlab-ci.yml files, configures pipeline stages, defines CI jobs and runners, sets up deployment workflows, and generates reusable GitLab CI/CD templates following current best practices and security standards. Use when users ask to create or build a GitLab CI/CD pipeline, CI config, build pipeline, deploy pipeline, GitLab YAML, CI jobs, or any .gitlab-ci.yml configuration from scratch or for a new project.
- ▌ Gitlab CI Validator · pantheon-org bundleValidates .gitlab-ci.yml syntax, detects security misconfigurations in job definitions, checks for deprecated keywords, ensures proper stage ordering, and audits pipeline configurations for best practices. Use when working with .gitlab-ci.yml files, validating GitLab CI/CD pipeline syntax, debugging configuration errors, checking for hardcoded secrets or credentials in pipeline jobs, optimizing pipeline performance with DAG or cache, or performing security audits on GitLab CI/CD configurations.
- ▌ Monty Python Esque · pantheon-org bundleGenerate an original British surrealist comedy sketch, script, or comic bit in the Monty Python tradition, built on absurd literalism, escalating internally-consistent illogic, bureaucratic pedantry, semantic argument, deadpan seriousness amid impossible premises, sudden non sequiturs, abrupt anticlimactic endings. Use this when a user asks for a new sketch, script, dialogue bit, or scene built on a mundane premise pushed to logical extremes. Do NOT use this to reproduce, quote, paraphrase, reword any actual Monty Python sketch, character, catchphrase (e.g. Dead Parrot, Spanish Inquisition, Ministry of Silly Walks, Argument Clinic); this is a generative skill for fresh original material, not a lookup, quotation, transcription tool. Not for slapstick, observational stand-up, roast comedy, American-style sitcom writing, where the humour depends on delivery, timing, rather than an escalating internally-consistent premise.
- ▌ Adr Creator · pantheon-org bundleCreates, lists, and supersedes Architecture Decision Records with the adr CLI, following the house ADR template. Use when recording an architectural decision, writing an ADR, documenting a technical choice, superseding a prior decision, numbering a new decision record, bootstrapping an ADR log under docs/adr.
- ▌ Plan Execute · pantheon-org bundleExecute an implementation plan with rigorous checklist-driven verification. Every task is pre-flighted, worked, validated with proof, and checked off. Every phase is validated as a whole. If proof is missing, the agent goes back. Honesty is non-negotiable — broken trust means the plan is not done. Triggers: 'implement this plan', 'execute the plan', 'start working on the plan', 'do the plan', 'carry out the phases', 'run the plan', 'work through the plan', 'carry out this plan', 'begin implementation'. Do NOT use for plans that have not been reviewed — use plan-review first.
- ▌ UI Debug Workflow · pantheon-org bundleDebug UI changes with a repeatable evidence-first workflow. Use when validating visual regressions, reproducing frontend bugs, comparing baseline vs changed behavior, collecting screenshots/DOM/logs, or producing stakeholder-ready UI debug reports. Keywords: ui bug, visual regression, browser devtools, playwright, screenshot evidence, dom snapshot, frontend debugging.
- ▌ Pick Model · pantheon-org bundleRecommend optimal Claude model (haiku/sonnet/opus) for a task. Use when user asks "which model", "pick model", "model for", or before starting costly/complex tasks. Covers tech and non-tech tasks.
- ▌ Biome Complete · pantheon-org bundleComplete Biome toolchain guidance for real repository workflows. Use when users ask to configure biome.json, run lint or format commands, migrate from ESLint or Prettier, tune rule severity, fix formatter drift, or replace mixed ESLint+Prettier pipelines with Biome-only workflows.
- ▌ Mise Complete · pantheon-org bundleConfigure and operate Mise for deterministic developer environments. Use when installing runtime/tool versions, defining reusable tasks, managing layered environment variables, migrating from asdf/nvm/pyenv, or debugging mise.toml behavior in CI and local shells. Keywords: mise, mise.toml, tool versions, tasks, env, asdf migration, setup automation, dev environment.
- ▌ Context Index · pantheon-org bundleRegenerates the project's context index (index.yaml) from the YAML frontmatter across every context file, grouping entries by typology (findings/plans/guides/follow-ups/merge-requests/tickets/decisions/notes/research), and validates that each file carries the required frontmatter fields. Also computes which active files are ready to work on, from optional typed `blocks`/`blocked-by` dependency links (scripts/context-ready.sh). Use when the index is stale, context files were added, renamed, or removed, a pre-commit gate blocks a commit because a context file is missing frontmatter, or someone asks what's ready/unblocked/blocked across the context backlog. Do not use it to create new context files (use create-context-file instead), to hand-edit the index, or as a substitute for fixing frontmatter at the source.
- ▌ Risk Register · pantheon-org bundleMaintain docs/RISK_REGISTER.md, the living, append-only list of every deferred item, interim shortcut, and open architecture decision for this project. Use when a shortcut is taken, a decision is postponed, a follow-up is filed, or an existing entry is actually resolved. DO NOT use for accepted, finalized architecture decisions (use adr-capture instead), for session-local working notes that don't need to survive across the team (use context-file / the local scratch-notes directory instead), or for anything that must stay confidential (the register is a committed, team-visible doc). Triggers: 'add to risk register', 'log this as a risk', 'track this shortcut', 'this is a known gap', 'mark risk #N resolved', 'what's on the risk register', 'what's still open'.
- ▌ Probe · pantheon-org bundleSafe-to-fail experiment for Complex domain problems where cause-effect is only visible in retrospect. Two-phase: foreground qualify → background probe → sense result. Use when: probe, safe-to-fail, test hypothesis, experiment with hypothesis, Complex domain with hypothesis. NOT for brainstorming (use brainstorm) or known cause-effect (use investigate).
- ▌ Cache Audit · pantheon-org bundleAudit your Claude Code setup against prompt caching best practices. Checks ordering, tool stability, dynamic content handling, and hook injection patterns. Returns a scored report with specific fixes.
- ▌ Vault Fetch · pantheon-org bundleFetch a URL, extract its text content, and persist it as a semantic memory tagged with the source URL for future retrieval. Use when the user shares a link to documentation, a GitHub issue, a blog post, or any reference material that should be available across sessions without re-fetching.
- ▌ Jenkinsfile Generator · pantheon-org bundleGenerates Jenkinsfiles with stages, agents, parallel builds, post-build actions, and security scanning for Declarative and Scripted pipeline syntaxes. Use when creating a Jenkins pipeline script, Groovy pipeline, or build configuration; implementing CI/CD workflows, continuous integration, or build automation; adding Docker/Kubernetes deployments, matrix builds, parameterized pipelines, or DevSecOps security scanning to a Jenkins setup.
- ▌ Jenkinsfile Validator · pantheon-org bundleComprehensive toolkit for validating, linting, testing, and automating Jenkinsfile pipelines (both Declarative and Scripted). Use this skill when working with Jenkins pipeline files, validating pipeline syntax, checking best practices, debugging pipeline issues, or working with custom plugins.
- ▌ Bun Development · pantheon-org bundleComplete Bun.js ecosystem guidance for runtime APIs, file I/O, package management, testing, SQLite, and security; use proactively when setting up Bun projects, replacing Node.js APIs with Bun-native APIs, writing bun test suites, implementing Bun.serve services, using bun:sqlite with prepared statements, configuring workspaces and lockfiles, hardening shell and SQL boundaries, or optimizing Bun performance and migration workflows.
- ▌ Plain English · pantheon-org bundleTranslates technical content into plain English for non-technical stakeholders by converting jargon into business language, surfacing decisions and impact early, and producing actionable recommendations with clear ownership and timeline. Use when the user asks to simplify technical content, write an executive summary, explain something in layman's terms, rewrite for non-technical audiences, or translate jargon for management or stakeholders. Applies to document types such as technical reports, architecture decision records, incident summaries, risk assessments, and status updates. Distinct from general writing or documentation skills by its focus on audience identification, decision-first structure, and jargon elimination for non-technical readers.
- ▌ Sop Structure · pantheon-org bundleUse when structuring Standard Operating Procedures with proper sections, organization, and markdown formatting. Covers SOP anatomy and section organization.
- ▌ Bridge · pantheon-org bundleCapture cross-project connections on the fly. Use when you notice a shared pattern, people-bridge, knowledge cascade, narrative amplifier, or flywheel loop linking two projects. Persists structured YAML to a bridges directory. Triggers on: bridge, connects to, feeds into, same pattern as, cross-project link, archetype detection, bidirectional, one-way, active, potential, theoretical.
- ▌ Load Context · pantheon-org bundleResume session from CONTEXT-llm.md. Use when resuming work, loading saved context, continuing a previous session. Triggers include "load context", "resume session", "continue where I left off".
- ▌ Save Context · pantheon-org bundleSave session to CONTEXT-llm.md with conversation summary. Use when saving work, checkpointing progress, preserving session state. Triggers include "save context", "save session", "checkpoint", "save my progress".
- ▌ Vault Search · pantheon-org bundleSearch persistent memory for relevant context — including architectural decisions, resolved bugs, and implementation patterns — when the user asks about past decisions, when debugging a recurring issue, when uncertain whether something was already decided, or before re-implementing something that may have been done before. Use when the user says "do you remember…", "what did we decide about…", or "have we solved this before".
- ▌ Nasa Pm Lessons · pantheon-org bundleSurface a matched excerpt from Jerry Madden's NASA project-management aphorisms (LLIS #1956) at the moment it fits: incident root-cause sections; ticket refinement; plan drafting; status updates; escalation calls. Loads only one category at a time — never the full list, never more than three aphorisms per response. DO NOT use this for regulatory, legal, or prize-dispute decisions; route those to Legal/Compliance/DPO. Triggers: 'root cause', 'refine this ticket', 'draft a plan', 'status update', 'should I escalate', 'stakeholder comms'.
- ▌ Tech Evaluation · pantheon-org bundleInvestigate a candidate library, dependency, or file format against a fixed question set and end with exactly one cited recommendation (adopt / keep_current / reject / needs_more_research) -- never "it depends." Validates the structured output against a JSON schema before writing a human-readable finding. Use when choosing between candidate npm packages, dependencies, or file formats for a specific integration point, or when a plan or ADR decision hinges on an unverified factual claim about a library (does it escape by default, does it bundle cleanly, is it maintained). Do NOT use for one-line version lookups, purely subjective preference calls with no verifiable claim, or a technology choice already settled by an existing ADR -- supersede the ADR instead. Triggers: "evaluate this library", "investigate this dependency", "compare X vs Y", "properly evaluate this technology", "which format should we use", "is this package maintained".
- ▌ Vault Capture · pantheon-org bundleCaptures an important insight, decision, constraint, pattern, or discovery to persistent memory via the vault CLI — distinct from general note-taking in that entries are tagged, tiered, and retrievable across future sessions. Use when the user says "save this", "remember this", "note for later", "don't forget", or "keep this in mind", or when the conversation produces something worth preserving: architectural decisions, recurring bugs, hard-won constraints, naming conventions, or user preferences.
- ▌ Logql Generator · pantheon-org bundleGenerate label matchers, line filters, log aggregations, and metric queries in LogQL (Loki Query Language) following current standards and conventions. Use this skill when creating new LogQL queries, implementing log analysis dashboards, alerting rules, or troubleshooting with Loki.
- ▌ Retrospect Collab · pantheon-org bundleAnalyze collaboration patterns (HOW) and compute metrics from captured sessions. Use when reviewing collaboration quality, analyzing human-AI interaction, computing session metrics. Triggers include "retrospect collab", "collaboration analysis", "session patterns", "how am I collaborating".
- ▌ Retrospect Domain · pantheon-org bundleAnalyze domain insights (WHAT/WHY learned) from captured sessions. Use when reviewing learnings, extracting patterns, analyzing decisions. Triggers include "retrospect domain", "domain analysis", "what did I learn", "session insights".
- ▌ Create Context · pantheon-org bundleCreate baseline context from .context/session/in/ folder with manifest-driven organization (run once per project). Use when bootstrapping project context, setting up .context/session/ctx/ snapshot. Triggers include "create context", "bootstrap context", "setup context", "init context".
- ▌ Github Actions Generator · pantheon-org bundleGenerates production-ready GitHub Actions workflows, custom actions, and CI/CD configurations following security and performance standards. Creates CI/CD pipelines, test workflows, deployment configurations, matrix builds, caching strategies, composite actions, Docker actions, JavaScript actions, and reusable workflows. Use when creating or scaffolding GHA resources, writing .github/workflows YAML files, setting up build automation, implementing deployment pipelines, adding security scanning, or building reusable actions — including triggers like 'create a workflow', 'build a pipeline', 'add CI', 'set up GHA', or 'generate a YAML workflow'.
- ▌ Github Actions Validator · pantheon-org bundleComprehensive toolkit for validating, linting, and testing GitHub Actions workflow files, custom local actions, and public actions. Use this skill when working with GitHub Actions YAML files (.github/workflows/*.yml), validating workflow syntax, testing workflow execution with act, or debugging workflow issues.
- ▌ Cunk Esque Mockumentary · pantheon-org bundleGenerate an original mockumentary presenter-satire segment, documentary narration plus an expert-interview scene, in a sincere-ignorance deadpan style. The presenter is a supremely confident, credential-free character who states garbled misunderstandings as flat fact; a genuine credentialed expert answers with strained, patient sincerity. Trigger this skill for requests to write, draft, punch up, or extend a mockumentary voiceover, deadpan documentary narration, faux-expert interview scene, satirical documentary script segment. Do NOT trigger for stand-up material, self-aware sketch comedy, roast-style insult comedy, hostile interview dialogue, straight factual documentary writing, reproduction of a real broadcaster's actual presenter, character, verbatim lines. This skill only produces new, original material based on the structural technique, not a copy of real broadcast content.
- ▌ Mermaid Diagrams · pantheon-org bundleComprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to "diagram", "visualize", "model", "map out", "show the flow", or when explaining system architecture, database design, code structure, or user/application flows.
- ▌ Cdk Nag · pantheon-org bundleEnforce AWS CDK security and compliance controls with cdk-nag. Use when adding rule packs, triaging findings, writing justified suppressions, integrating checks in CI/CD, or preventing insecure infrastructure patterns in CDK stacks.
- ▌ Promql Generator · pantheon-org bundleGenerate PromQL queries for calculating error rates, aggregating metrics across labels, creating histogram percentiles, writing recording rules, and building SLO burn-rate alerts following Prometheus best practices. Use when creating new PromQL queries, implementing monitoring and alerting rules, building observability dashboards, working with Prometheus metrics (counters, gauges, histograms, summaries), or applying RED (Rate, Errors, Duration) and USE (Utilization, Saturation, Errors) monitoring patterns.
- ▌ Promql Validator · pantheon-org bundleComprehensive toolkit for validating, optimizing, and understanding Prometheus Query Language (PromQL) queries. Use this skill when working with PromQL queries, prometheus queries, metrics queries, alerting rules, recording rules, or grafana dashboards to check syntax, detect anti-patterns, identify optimization opportunities, and interactively plan queries with users.
- ▌ Challenge · pantheon-org bundleChallenge, push back, play devil's advocate on AI output. Use when: challenge this, are you sure, push back, prove it, what if you're wrong, devil's advocate, stress test, poke holes, second opinion, sanity check, too confident, really?, question this decision. Subcommands: anchor (committed too fast), verify (facts wrong?), framing (wrong problem?), deep (full devil's advocate in separate context).
- ▌ Socratic Method · pantheon-org bundleRefine vague, complex, or high-stakes prompts through Socratic dialogue — surfaces hidden assumptions, probes reasoning, and iterates toward clarity before committing to an implementation.
- ▌ Azure Pipelines Generator · pantheon-org bundleGenerates production-ready Azure DevOps Pipelines (azure-pipelines.yml) following current best practices, security standards, and naming conventions. Use when creating or updating ADO YAML pipelines, configuring build triggers, defining multi-stage deployments, setting up template references, creating variable groups, writing release pipelines, or structuring CI/CD workflows for Azure DevOps Services or Azure DevOps Server. Handles build pipelines, YAML pipelines, Docker container builds, Kubernetes/AKS deployments, language-specific pipelines (.NET, Node.js, Python, Go, Java), and reusable step/job/stage templates. All generated configurations are validated using the devops-skills:azure-pipelines-validator skill before delivery.
- ▌ Azure Pipelines Validator · pantheon-org bundleValidates, lints, and security-scans Azure DevOps Pipeline configurations (azure-pipelines.yml / azure-pipelines.yaml). Use when working with ADO pipelines, YAML pipeline files, or CI/CD configurations in Azure DevOps — including validating YAML syntax and schema, detecting hardcoded secrets or credentials, checking for deprecated or unpinned task versions, enforcing best practices (caching, timeouts, display names), performing pipeline security audits, or reviewing azure-pipelines.yml before merging. Trigger terms: azure-pipelines.yml, ADO pipeline, Azure Pipelines, YAML pipeline, CI/CD validation, pipeline security scan, DevOps configuration review.
- ▌ Typescript Advanced · pantheon-org bundleComprehensive TypeScript guidance covering compiler configuration, advanced types, utility types, type guards, strict mode workflows, and documentation patterns; use when configuring tsconfig, designing complex generics, making illegal states unrepresentable, fixing type errors, or writing testable and maintainable type-safe APIs.
- ▌ Defuddle · pantheon-org bundleExtract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page.
- ▌ Test Driven Development · pantheon-org bundleGuides TDD (test-driven development) with red-green-refactor workflows, test-first feature delivery, bug reproduction through failing tests, behavior-focused assertions, and refactoring safety. Use when writing unit tests, implementing new functions, adding test coverage, fixing regressions, changing APIs, or restructuring code under test — especially when a user says "write tests first", "TDD", or "test before code".
- ▌ Guided Interview · pantheon-org bundleConduct a structured, one-question-at-a-time interview to explore a specific topic or decision — each question offers 3-4 concrete, mutually exclusive options plus a free-text path, and later questions adapt to prior answers rather than following a fixed script. Ends with a recap the user confirms before finalizing, and only then produces a synthesized answer or (when the interview clearly feeds downstream work) a written brief. NOT for open-ended ambiguity-surfacing (use socratic-method) or single-fact lookups.
- ▌ Rules Management · pantheon-org bundleManage project-level agent behavioural rules recorded in a single rules file. Use when the user says 'new rule', 'add a rule', 'record that', 'make a rule that', 'note this', 'take note of', 'new instruction', or asks to codify an agent directive. Read the rules file to check existing rules before adding a new one. DO NOT use for ephemeral notes, one-off instructions, or instructions that belong in the project's own agent-facing docs. Triggers: 'new rule', 'add a rule', 'record that', 'make a rule', 'codify this', 'rule about', 'create a directive', 'note this', 'take note of', 'new instruction'.
- ▌ Markdown Authoring · pantheon-org bundleAuthor high-quality Markdown documentation with deterministic structure, lint compliance, and CI integration. Use when writing README files, creating docs pages, fixing markdownlint failures, defining style rules, or wiring markdown checks into pre-commit and pipelines. Keywords: markdown, markdownlint, readme, docs, headings, lists, code fences, links, images, lint config, ci, documentation style.
- ▌ Ansible Generator · pantheon-org bundleGenerates, validates, and refactors production-ready Ansible playbooks, roles, task files, and inventory configurations following current best practices. Use when the user asks to create, build, or generate Ansible automation, YAML playbooks, infrastructure as code, configuration management files, DevOps roles, or .yml files for Ansible — including requests like "create a playbook to...", "build a role for...", "generate an inventory for...", or "set up Ansible to automate...". Automatically validates all output using the devops-skills:ansible-validator skill.
- ▌ Ansible Validator · pantheon-org bundleComprehensive toolkit for validating, linting, testing, and automating Ansible playbooks, roles, and collections. Use this skill when working with Ansible files (.yml, .yaml playbooks, roles, inventories), validating automation code, debugging playbook execution, performing dry-run testing with check mode, or working with custom modules and collections.
- ▌ Create Context File · pantheon-org bundleCreates a structured, date-stamped context file filed by typology (findings, plans, guides, follow-ups, merge-requests, tickets, decisions, notes, research) with YAML frontmatter. Use when saving a finding, writing a plan, capturing a guide, recording a decision, logging a follow-up, filing a merge-request note, plus ticket write-ups.
- ▌ Colyseus Multiplayer · pantheon-org bundleBuild authoritative real-time multiplayer servers with Colyseus 0.17+. Use when implementing rooms, schema state sync, client message validation, matchmaking, authentication, reconnection handling, or server-side anti-cheat constraints. Keywords: colyseus, room lifecycle, schema, multiplayer, websocket, matchmaking, onJoin, onLeave, onDrop, allowReconnection.
- ▌ Vault Consolidate · pantheon-org bundlePropose or apply consolidation of episodic memories into semantic ones, combining related episodic captures into higher-level semantic summary notes. Use after a long session or when the user asks to clean up, organise, summarise, merge, or declutter memories, or requests memory cleanup or memory management. Always run --propose first so the user can review before --apply commits changes to the vault.
- ▌ Brooker Esque Media Satire · pantheon-org bundleGenerate original, misanthropic media/technology satire in the Charlie-Brooker tradition — a cynical column, monologue, short story built from one extended grotesque metaphor, self-loathing narration, hyperbole-and-bathos, corporate-jargon translation, plus a near-future premise that escalates one believable step at a time toward a bleak, deflating ending. Use for a satirical takedown of a TV show, app, gadget, news format, or social-media trend, plus dystopian near-future short stories about a plausible technology/social mechanic. Do NOT use for mockumentary/character-voice sketches, deadpan two-hander political interviews, observational stand-up; also not for reproducing a real writer's actual column, script, episode — this skill only generates new material inspired by the technique, never a copy.
- ▌ Notebooklm · pantheon-org bundleQuery Google NotebookLM notebooks directly for source-grounded, citation-backed answers from your uploaded documents. Includes browser automation, library management, and persistent authentication.
- ▌ K8S YAML Generator · pantheon-org bundleComprehensive toolkit for generating, validating, and managing Kubernetes YAML resources. Use this skill when creating Kubernetes manifests (Deployments, Services, ConfigMaps, StatefulSets, etc.), working with Custom Resource Definitions (CRDs), or generating production-ready K8s configurations.
- ▌ K8S YAML Validator · pantheon-org bundleComprehensive toolkit for validating, linting, and testing Kubernetes YAML resources. Use this skill when validating Kubernetes manifests, debugging YAML syntax errors, performing dry-run tests on clusters, or working with Custom Resource Definitions (CRDs) that require documentation lookup.
- ▌ Blast Radius · pantheon-org bundleFind what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust. DO NOT use for explaining how existing code works (use how instead) or investigating why it was built that way (use why instead). Triggers: blast radius of X, what could this break, is this change safe, review this diff, what am I missing in this change.
- ▌ Troubleshoot · pantheon-org bundleUse when user reports an error, bug, or something not working. Search-first troubleshooting with diagnostic phase. Triggers: debug, error, broken, not working, failing, crash, exception.
- ▌ Github Copilot Models · pantheon-org bundleQuery and display available GitHub Copilot AI models with their capabilities, context limits, and features. Use when: "what models are available", "show copilot models", "list github models", "check model capabilities", "switch models". Examples: - user: "What models can I use with GitHub Copilot?" → fetch and display available models - user: "Show me models with vision support" → filter models by capability - user: "Which model has the largest context window?" → compare model specifications - user: "List all GPT-5 models" → filter by model family
- ▌ Session Reflection · pantheon-org bundleConduct a two-question session-end reflection to catch blind spots and under-investigated areas before concluding. The agent surfaces its lowest-confidence work items and identifies what the user might be missing, then offers to investigate. Based on a Reddit-post technique combining an LLM-suggested confidence audit with Sam Altman's blind-spot question. Do NOT trigger for brief single-answer queries, CI contexts, or in the middle of active work -- only when a session appears to be concluding. Triggers: 'wrap up', 'we're done', 'conclude', 'session end', 'final review', 'before we go', 'sign off', 'that's all', 'anything else', 'finished', 'reflection', 'confidence check', 'blind spot', 'what are you missing', 'rate your confidence', 'review the session'.
- ▌ Gervais Esque Cringe Satire · pantheon-org bundleGenerate original cringe comedy and provocateur stand-up material in two modes — (1) character-based cringe scenes/sketches with an oblivious, self-important figure (boss, host, celebrity) surrounded by uncomfortable onlookers, mockumentary-style; (2) direct-address stand-up bits, monologues, roast lines that state a taboo truth bluntly, without hedging, then escalate. Trigger for requests for an original sketch, scene, monologue, roast bit, cringe scene, blunt stand-up line, built on oblivious self-delusion, awkward silence, escalating humiliation, mock self-congratulation, flippant treatment of solemn subjects. Do NOT use this skill for gentle observational humor, warm sitcom banter, wordplay/puns with no discomfort element, requests to reproduce/paraphrase a real comedian's actual routine, script, special — this skill generates new material; it does not mimic an existing performance.
- ▌ Conventional Commits · pantheon-org bundleGenerates and formats git commit messages following the Conventional Commits specification. Use when the user asks for help writing commit messages, formatting git commits, wants to write a commit msg for staged changes, needs to produce a changelog entry, or mentions conventional commits, semantic versioning, or version bumps. Analyzes diffs or change descriptions, selects the correct type/scope, writes an imperative-mood header under 72 characters, and composes optional body and footer sections including breaking-change notation.
- ▌ Journal Entry Import · pantheon-org bundleReconstructs journal entries from external systems: bulk-imports a historical work log from a legacy source system such as a deprecated Confluence page into dated entries, enriches ticket references with self-contained detail entries reconstructed from an issue tracker, and annotates links to systems that have since moved such as a Bitbucket-to-GitLab migration. Use when asked to import an old journal, migrate a log into the journal format, turn ticket mentions into entries, expand a log with ticket detail, or point old links at a new host. This is not for repairing frontmatter on entries that already exist in this format, which is the journal CLI's own backfill command. Produces validated dated entries compatible with journal-entry-creator, complete with bidirectional cross-links and annotated external links.
- ▌ JSON Canvas · pantheon-org bundleCreate and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.
- ▌ Triage Tool · pantheon-org bundleTriage a tool or library into a structured reference summary for the research repo. Use when given a GitHub URL, npm package, PyPI package, or CLI tool name. Creates references/{slug}.md with architecture overview and scope assessment; adds REVIEWED.md entry and REFERENCE_INDEX.md row. Triggers: triage tool, add tool, analyse tool, GitHub project, npm package, PyPI package, library, framework, CLI tool, MCP server, open source project.
- ▌ Terraform Generator · pantheon-org bundleGenerate Terraform modules, configure providers, define variables and outputs, set up remote state backends, and write production-ready HCL (.tf files) following current standards. Use when creating new Terraform resources, building Terraform projects, writing infrastructure as code (IaC), scaffolding AWS/Azure/GCP cloud infrastructure, working with terraform plan/apply workflows, or structuring multi-environment configurations.
- ▌ Terraform Validator · pantheon-org bundleComprehensive toolkit for validating, linting, testing, and automating Terraform configurations and HCL files. Use this skill when working with Terraform files (.tf, .tfvars), validating infrastructure-as-code, debugging Terraform configurations, performing dry-run testing with terraform plan, or working with custom providers and modules.
- ▌ Nx Bun Integration · pantheon-org bundleIntegrate Bun runtime into Nx monorepos with deterministic plugin setup, executor configuration, migration from Node.js toolchains, and cache-aware build/test workflows; use when adding the nx-bun plugin, converting projects, or standardizing Bun targets across Nx workspaces.
- ▌ Frame Problem · pantheon-org bundleSense-making before action. Classify problem using Cynefin triangulation (3 tests + decomposition) to route to the right skill chain. Use when: frame, what approach, how should I start, which skill, where to begin, unsure what to do. NOT for known tasks — just do them.
- ▌ Comedy Style Skill Generator · pantheon-org bundleGenerate a new, reusable comedy-writing SKILL.md for a requested comedic tradition — real, generic, or invented — by extracting its transferable comic mechanics (premise construction, escalation pattern, rhythm, rhetorical devices) into concrete, actionable writing rules instead of vague adjectives, and by converting any living performer's persona into technique rather than voice-imitation. Use this when a user asks to create a comedy skill for a style, or a skill "like" a comedian or show, and wants a complete SKILL.md file back. Do NOT use this to write comedic material directly (that is the generated skill's job, not this one's), for non-comedy skill generation, or to produce a skill whose body just says "be funny" or "make it absurd" without concrete mechanics.
- ▌ Journal Entry Creator · pantheon-org bundleCreate structured journal entries with YAML frontmatter, template-based sections, and compliance validation. Use when user asks to 'create journal entry', 'new journal', 'document [topic]', 'journal about [topic]', or needs to create timestamped .md files in YYYY/MM/ directories. Supports six entry types: general journal entries, troubleshooting sessions, learning notes, article summaries, ticket-refinement sessions, and ticket-kickoff sessions. Keywords: journal, documentation, troubleshooting, learning, article-summary, ticket-refinement, ticket-kickoff, YAML frontmatter, template schemas, validation.
- ▌ Obsidian CLI · pantheon-org bundleInteract with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.
- ▌ Triage Paper · pantheon-org bundleTriage an academic paper into a structured reference summary for the research repo. Use when given an arxiv ID, arxiv URL, DOI, or paper PDF. Creates references/{slug}.md; adds REVIEWED.md entry and REFERENCE_INDEX.md row. Triggers: triage paper, add paper, analyse paper, review paper, literature review, survey paper, benchmark paper, deep dive paper, arxiv, DOI.
- ▌ Cfn Template Compare · pantheon-org bundleCompares deployed CloudFormation templates with locally synthesized CDK templates to detect drift, validate changes, and ensure consistency before deployment. Use when the user wants to compare CDK output with a deployed stack, check for infrastructure drift, run a pre-deployment validation, audit IAM or security changes, investigate a failing deployment, or perform a 'cdk diff'-style review. Triggered by phrases like 'compare templates', 'check for drift', 'cfn drift', 'stack comparison', 'infrastructure drift detection', 'safe to deploy', or 'what changed in my CDK stack'.