← all publishers

opsmill

@opsmill source repo

Report this profile Claim this profile

• 95 skills
• 0 followers
• 3 hours ago last updated

1. ▌
   Speckit Agent Context Update · opsmill

   Refresh the managed Spec Kit section in coding agent context file(s)
   0
   installs
2. ▌
   Speckit Opsmill Retrospect · opsmill

   Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.
   0
   installs
3. ▌
   Infrahub Analyst · opsmill bundle

   Analyze and correlate Infrahub data using the MCP server. Use when querying live infrastructure data to answer operational questions, detect drift, correlate node types, investigate service impact, check maintenance windows, or produce ad-hoc reports — without writing pipeline code.
   0
   installs
4. ▌
   Infrahub Menu Creator · opsmill bundle

   Create and manage Infrahub custom menus. Use when designing navigation menus, organizing node types in the UI, or customizing the Infrahub web interface sidebar.
   0
   installs
5. ▌
   Infrahub Repo Auditor · opsmill bundle

   Audit an Infrahub repository against all best practices and rules. Use when reviewing a project for compliance, onboarding to an existing repo, or before deployment to catch issues early.
   0
   installs
6. ▌
   Infrahub Check Creator · opsmill bundle

   Create and manage Infrahub check definitions. Use when writing validation logic, creating Python checks that run in proposed change pipelines, or building data quality guards for Infrahub.
   0
   installs
7. ▌
   Infrahub Object Creator · opsmill bundle

   Create and manage Infrahub object data files. Use when populating infrastructure data, creating device instances, locations, organizations, module installations, or any other data objects for an Infrahub repository.
   0
   installs
8. ▌
   Infrahub Schema Creator · opsmill bundle

   Create, validate, and modify Infrahub schemas. Use when designing data models, creating schema nodes with attributes and relationships, validating schema definitions, or planning schema migrations for Infrahub.
   0
   installs
9. ▌
   Infrahub Generator Creator · opsmill bundle

   Create and manage Infrahub Generators. Use when building design-driven automation that creates infrastructure objects from templates, topology definitions, or any design-to-implementation workflow in Infrahub.
   0
   installs
10. ▌
    Infrahub Transform Creator · opsmill bundle

    Create and manage Infrahub transforms. Use when building data transformations, config generation, or any workflow that converts Infrahub data into a different format (JSON, text, CSV, device configs) using Python or Jinja2 templates.
    0
    installs
11. ▌
    Creating Prd · opsmill

    Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports.
    0
    installs
12. ▌
    Quality Gates · opsmill bundle

    Shared in-workflow quality gates for code/PR skills — the gate model, trust tiers, and the three primitives (evidence-before-done, independent judge, anti-gaming). DO NOT TRIGGER directly — referenced by consumer skills via relative path.
    0
    installs
13. ▌
    Speckit Git Feature · opsmill

    Validate Jira/JPD ticket reference and create a feature branch
    0
    installs
14. ▌
    Upgrade Infrahub · opsmill

    Upgrade the Infrahub platform version in this project. Handles downloading the new compose file, upgrading the SDK, updating version references across Dockerfile, docker-compose.override.yml, and .envrc, and rebuilding the Docker image. Use this skill whenever the user asks to upgrade, bump, or update the Infrahub version — even if they just say something like "bump infrahub to 1.9" or "upgrade to latest infrahub" or "update infrahub version".
    0
    installs
15. ▌
    Opsmill Dev Pr · opsmill

    Opens a pull request, publishing the current branch as a PR. TRIGGER when: the user wants to open a pull request, publish the current branch as a PR, or take the current work through to an open PR. DO NOT TRIGGER when: only committing changes → opsmill-dev-commit; babysitting CI after the PR is already open → opsmill-dev-monitoring-pull-requests.
    0
    installs
16. ▌
    Opsmill Dev Commit · opsmill

    Stages and commits the current changes onto a safe working branch, enforcing branch discipline and optionally pushing upstream. TRIGGER when: the user wants to commit, save, or check in the current changes. DO NOT TRIGGER when: opening a pull request → opsmill-dev-pr.
    0
    installs
17. ▌
    Opsmill Dev Rebase · opsmill

    Rebases a feature branch onto its latest base, resolving conflicts while preserving the intent of local changes, optionally force-pushing and watching CI afterward. TRIGGER when: the user wants to rebase a feature branch, update a branch against its base, or replay local work on top of the latest upstream. DO NOT TRIGGER when: merging a release branch into dev → opsmill-dev-merging-branches; only watching CI on an already-open PR → opsmill-dev-monitoring-pull-requests.
    0
    installs
18. ▌
    Opsmill Dev Fixing Bugs · opsmill

    Implements and validates the fix for a bug once a failing reproduction test exists. TRIGGER when: a bug has a failing reproduction test and you are ready to make it pass, implementing the root-cause fix, the final step of the bug-fixing pipeline. DO NOT TRIGGER when: no reproduction test exists yet → opsmill-dev-test-driving-bugs; still diagnosing, or asked to fix a bug with no analysis or reproduction test yet → opsmill-dev-analyzing-bugs.
    0
    installs
19. ▌
    Opsmill Dev Creating Prd · opsmill

    Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → opsmill-dev-creating-issues; the idea has not been stress-tested yet → opsmill-dev-grilling-ideas first; bug reports.
    0
    installs
20. ▌
    Opsmill Dev Analyzing Bugs · opsmill

    Performs root-cause analysis of a bug — from a GitHub issue, an issue URL, or a free-text description — before any reproduction or fix is written. TRIGGER when: triaging or diagnosing a bug, investigating why something misbehaves, an issue number/URL handed over for analysis, needing the root cause before touching code. DO NOT TRIGGER when: a failing reproduction test already exists and you are ready to fix → opsmill-dev-fixing-bugs; writing that reproduction test → opsmill-dev-test-driving-bugs; capturing a new bug as a ticket → opsmill-dev-creating-issues.
    0
    installs
21. ▌
    Opsmill Dev Grilling Ideas · opsmill

    Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → opsmill-dev-creating-prd.
    0
    installs
22. ▌
    Opsmill Dev Creating Issues · opsmill

    Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking work into multiple issues or planning a body of work → a planning skill; writing a full Product Requirements Document → opsmill-dev-creating-prd; the idea is still fuzzy and unhardened → opsmill-dev-grilling-ideas first.
    0
    installs
23. ▌
    Opsmill Dev Merging Branches · opsmill

    Merges one long-lived branch into another (e.g. a release branch into the main development branch) on a fresh integration branch, or takes over a stalled merge-conflict PR. TRIGGER when: phrasings like "merge <release> into <dev>", "take over this merge-conflict PR", or a GitHub PR link for a branch sync. DO NOT TRIGGER when: replaying local work onto the latest base → opsmill-dev-rebase; opening a pull request → opsmill-dev-pr.
    0
    installs
24. ▌
    Opsmill Dev Pruning Residues · opsmill

    Use when an artifact has been argued, iterated, or debugged into its current shape and now carries rationale that only made sense in the process that produced it. Applies to docs, code comments, commit and PR/issue text, and config-file comments. Sweeps the artifact so it states what it does, not why it was argued into that shape. Triggers on "tidy this", "strip the residue", "make this read standalone".
    0
    installs
25. ▌
    Opsmill Dev Backporting Fixes · opsmill

    Ports an existing fix from one long-lived branch to another (e.g. a stable fix landed on the development branch), adapting it to the target branch's current code rather than cherry-picking blindly. TRIGGER when: phrasings like "backport <fix/PR/commit> to <branch>", "port this stable fix to develop", "land <ticket> on <branch> too", or a fix that already exists on one branch has to land on another. DO NOT TRIGGER when: syncing one whole branch into another wholesale → opsmill-dev-merging-branches; replaying local work onto its base → opsmill-dev-rebase; fixing a brand-new bug that has no existing fix → opsmill-dev-analyzing-bugs / opsmill-dev-fixing-bugs.
    0
    installs
26. ▌
    Opsmill Dev Test Driving Bugs · opsmill

    Writes a single failing test that reproduces a bug after its root-cause analysis is complete, before any fix is written. TRIGGER when: a bug has a completed root-cause analysis and you need the failing reproduction test, writing a test that proves a bug exists, the second step of the bug-fixing pipeline. DO NOT TRIGGER when: still triaging or diagnosing the bug → opsmill-dev-analyzing-bugs; implementing the fix once the test exists → opsmill-dev-fixing-bugs; general feature test-first work → superpowers test-driven-development.
    0
    installs
27. ▌
    Opsmill Dev Monitoring Pull Requests · opsmill

    Watches an open pull request's CI until green and fixes failing checks. TRIGGER when: the user wants to watch a pull request's CI, babysit a PR until it goes green, or fix failing CI checks on an open PR. DO NOT TRIGGER when: opening the PR in the first place → opsmill-dev-pr; rebasing the branch onto its base → opsmill-dev-rebase.
    0
    installs
28. ▌
    Opsmill Dev Analyzing Dependency Bumps · opsmill

    Produces a breaking-change / deprecation / opportunity report for a dependency-bump PR, grounded in how this codebase actually uses each bumped package, not the changelog alone. TRIGGER when: the user gives a PR URL or number for a dependency version bump (Dependabot, Renovate, or hand-rolled) and asks what could break, what changed, or whether it is safe to merge (e.g. "scan this dependabot PR", "what breaks if we take this bump", "is <PR url> safe to merge"). DO NOT TRIGGER when: the PR is a feature or bugfix rather than a dependency version bump → a code-review or bug skill instead.
    0
    installs
29. ▌
    Infrahub Importing Data · opsmill bundle

    Converts CSV/TSV inputs into Infrahub object YAML and loads them onto a fresh branch. Handles a single file, a folder of files, an explicit list of paths, and one-big-denormalized-sheet exports. TRIGGER when: importing CSV, loading CSV/TSV into Infrahub, ingesting spreadsheet data, converting CSV to Infrahub objects, splitting a denormalized CSV across multiple kinds. DO NOT TRIGGER when: running `infrahubctl import load` against an LDJSON dump (different format and tool), designing or modifying schemas (this skill is read-only against the schema and fails closed on unmapped columns), exporting data from Infrahub (use `infrahubctl object get -o csv` for single-kind export), or ingesting JSON/XLSX (v1 is CSV+TSV only).
    0
    installs
30. ▌
    Infrahub Reporting Issues · opsmill bundle

    Reports bugs and feature requests against the right Infrahub-ecosystem GitHub repository. Classifies the request, routes it (with the main `opsmill/infrahub` repo as the safe fallback when in doubt), searches for existing duplicates, gathers conservative environment info for bugs, and prepares the issue for the user to review before any submission. TRIGGER when: user wants to report a bug, file an issue, request a feature, open a ticket, or escalate a problem in any opsmill/infrahub-* project (SDK, Ansible, VS Code, MCP, Helm, schema-library, sync, backup, nornir, skills). DO NOT TRIGGER when: the user wants to fix the bug themselves locally, write a test, or debug code without filing.
    0
    installs
31. ▌
    Infrahub Reporting Skill Gaps · opsmill bundle

    Turns friction from an Infrahub skill session into a reviewed GitHub issue about an Infrahub skill's guidance. Infrahub skills fail quietly: a missing or unclear rule does not crash, it produces extra round trips and repeated user nudges. This skill gathers evidence of that friction, checks the tracker for an existing report, works out whether the skill or the underlying product is at fault, and drafts a proposed rule change. It never files anything itself: it hands the redacted draft to infrahub-reporting-issues, which shows it to the user and gets explicit approval before any submission. TRIGGER when: accepting a friction offer, the user says "report skill friction", asks why an Infrahub skill kept failing or needed so many retries, or wants a gap in an Infrahub skill's guidance reported. DO NOT TRIGGER when: reporting a bug in Infrahub itself or any other opsmill/infrahub-* product (use infrahub-reporting-issues instead), or for ordinary Infrahub work where nothing went wrong.
    0
    installs
32. ▌
    Infrahub Analyzing Diagnostics · opsmill bundle

    Analyze an already-collected infrahub-collect diagnostic bundle — traceback and failure triage across service logs, incident correlation, and known-issue matching against opsmill/infrahub GitHub issues. TRIGGER when: the user says they collected a diagnostic bundle, gives you a bundle path, or pastes bundle contents — and asks what's wrong, wants the logs or tracebacks analyzed, asks "what does this bundle say", wants errors triaged/correlated, or asks whether a crash is a known issue. DO NOT TRIGGER when: no bundle exists yet — collect one first (use infrahub-collecting-diagnostics), filing the issue itself (use infrahub-reporting-issues), or querying live data (use infrahub-analyzing-data).
    0
    installs
33. ▌
    Infrahub Collecting Diagnostics · opsmill bundle

    Collect a redacted local diagnostic bundle (logs, config, version, state) for an OpsMill expert hand-off. TRIGGER when: Infrahub is broken/failing/erroring, the user asks for help debugging, wants to collect logs/diagnostics, prepares a hand-off for OpsMill support, or reports a crash/timeout/connection issue (upgrade failure, stuck branch, container CrashLoopBackOff, 500s, OOM). DO NOT TRIGGER when: a bundle has already been collected and the user wants it analyzed (use infrahub-analyzing-diagnostics), filing a public GitHub issue (use infrahub-reporting-issues), or running operational queries (use infrahub-analyzing-data).
    0
    installs
34. ▌
    Speckit Review Run · opsmill

    Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.
    0
    installs
35. ▌
    Speckit Critique Run · opsmill

    Perform a dual-lens critical review of the specification and plan from both product strategy and engineering risk perspectives before implementation.
    0
    installs
36. ▌
    Speckit Opsmill Auto · opsmill

    Run the full speckit workflow end-to-end — specify, plan, critique, tasks, implement, review — making all decisions autonomously. Stops before extract; run that manually.
    0
    installs
37. ▌
    Speckit Opsmill Prep · opsmill

    Run the speckit preparation phases end-to-end — specify, plan, critique, tasks — making all decisions autonomously. Stops before implementation.
    0
    installs
38. ▌
    Speckit Opsmill Summary · opsmill

    Produce a flow-level summary of the current Claude Code session — executive summary, chronological timeline, and outcomes — written into the active feature directory next to spec.md / plan.md.
    0
    installs
39. ▌
    Pr · opsmill

    Opens a pull request, publishing the current branch as a PR. TRIGGER when: the user wants to open a pull request, publish the current branch as a PR, or take the current work through to an open PR. DO NOT TRIGGER when: only committing changes → commit; babysitting CI after the PR is already open → monitoring-pull-requests.
    0
    installs
40. ▌
    Commit · opsmill

    Stages and commits the current changes onto a safe working branch, enforcing branch discipline and optionally pushing upstream. TRIGGER when: the user wants to commit, save, or check in the current changes. DO NOT TRIGGER when: opening a pull request → pr.
    0
    installs
41. ▌
    Rebase · opsmill

    Rebases a feature branch onto its latest base, resolving conflicts while preserving the intent of local changes, optionally force-pushing and watching CI afterward. TRIGGER when: the user wants to rebase a feature branch, update a branch against its base, or replay local work on top of the latest upstream. DO NOT TRIGGER when: merging a release branch into dev → merging-branches; only watching CI on an already-open PR → monitoring-pull-requests.
    0
    installs
42. ▌
    Feature Flow · opsmill

    Multi-phase orchestrator for a feature: spec → plan → implement → review → CI gate → PR. Uses parallel agents for divergent thinking and a single synthesizer between phases. Trigger when the user says 'start the feature flow', 'run feature-flow', or names a ticket and asks to drive it end to end.
    0
    installs
43. ▌
    Audit Docs · opsmill

    Audits internal (dev/) and external (docs/) documentation completeness for a feature, subject, or set of existing docs, maps changes indicated by the user, across Infrahub's documentation layers, reports gaps, and optionally applies the fixes. TRIGGER when: the user wants to audit or check documentation coverage, find doc gaps after a feature branch, or verify docs are still current for a subject or specific files. DO NOT TRIGGER when: authoring new documentation from scratch → use the add-docs flow; only linting/formatting Markdown → run `uv run invoke docs.lint`.
    0
    installs
44. ▌
    Capture Knowledge · opsmill

    Capture non-obvious facts learned while working into dev/knowledge/, dev/guidelines/, or dev/guides/ so future agents understand the code faster. Trigger when the user says 'capture this', 'document this', 'we should write that down', or autonomously at the end of a feature when something non-obvious was learned.
    0
    installs
45. ▌
    Grilling Ideas · opsmill

    Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.
    0
    installs
46. ▌
    Creating Issues · opsmill

    Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking work into multiple issues or planning a body of work → a planning skill; writing a full Product Requirements Document → creating-prd; the idea is still fuzzy and unhardened → grilling-ideas first.
    0
    installs
47. ▌
    Harvesting Review · opsmill

    Mines a pull request's review threads for lessons that generalize beyond that PR, reconstructs each against the actual code before deciding, checks whether it is already codified, and routes the genuinely-new, durable ones into Infrahub's internal documentation — `dev/knowledge/`, `dev/guides/`, `dev/guidelines/`, the `AGENTS.md` files, and `.agents/rules/` — proposing edits first and applying only with the user's approval. TRIGGER when: the user wants to turn PR review feedback into durable conventions, guidelines, or rules; capture recurring reviewer comments as internal documentation; or check whether review lessons are reflected in the knowledge/guides/guidelines/AGENTS.md/rules layer. DO NOT TRIGGER when: sweeping a feature's changes for documentation coverage across all layers → use `audit-docs`; extracting knowledge from completed spec directories → `speckit-opsmill-extract`; only replying to or resolving review threads → normal git/gh flow.
    0
    installs
48. ▌
    Neo4j Cypher Guide · opsmill bundle

    Comprehensive guide for writing modern Neo4j Cypher queries. Essential for text2cypher MCP tools and LLMs generating Cypher queries. Covers removed/deprecated syntax, modern replacements, CALL subqueries for reads, COLLECT patterns, sorting best practices, set-based writes, and Quantified Path Patterns (QPP) for efficient graph traversal.
    0
    installs
49. ▌
    Migrate Feature Page · opsmill

    Migrate Infrahub docs feature pages from the legacy topic+guide pair into a cleaner structure (single merged page, hub+spokes, or tutorial extraction). Supports both single-feature migrations (one feature like Profiles or Webhooks) and section-wide migrations (a whole section like Branches & Change Control with multiple features migrated together) when the team has agreed on a section-wide restructure plan. Trigger when the user names a specific feature or section to migrate (e.g. "let's migrate profiles", "start the Resource Manager migration", "do the entire Branches & Change Control section"). Each migration is its own branch off `demo/groups-diataxis-example`, its own PR back to that branch.
    0
    installs
50. ▌
    Analyzing CI Flakiness · opsmill bundle

    Analyzes recent CI failures on pull requests to identify flaky tests, using retry outcomes (failed attempt → green re-run) and cross-PR recurrence as evidence, and maintains a local longitudinal ledger so flakiness can be tracked over time. TRIGGER when: the user wants to find flaky tests, correlate recent CI failures, check which tests fail across PRs or recover on retry, or refresh the flakiness trend report. DO NOT TRIGGER when: babysitting a single PR's CI until green → monitoring-pull-requests; diagnosing or fixing one specific failing test → the bug-analysis skills.
    0
    installs
51. ▌
    Speckit Opsmill Extract · opsmill

    Extract knowledge, guidelines, and ADRs from one or more completed spec directories into the project documentation system.
    0
    installs
52. ▌
    Monitoring Pull Requests · opsmill

    Watches an open pull request's CI until green and fixes failing checks. TRIGGER when: the user wants to watch a pull request's CI, babysit a PR until it goes green, or fix failing CI checks on an open PR. DO NOT TRIGGER when: opening the PR in the first place → pr; rebasing the branch onto its base → rebase.
    0
    installs
53. ▌
    Creating Changelog Entries · opsmill

    Use when you've fixed a bug, added a feature, or made any user-facing change in a project that uses Towncrier and need to record it for the changelog — before committing or opening a PR, or whenever asked to add a changelog entry, towncrier fragment, or news fragment.
    0
    installs
54. ▌
    Speckit Opsmill Implement · opsmill

    Run the speckit implementation phase chunk-by-chunk in clean-context subagents, then review, then produce a final report. Picks up from an existing tasks.md.
    0
    installs
55. ▌
    Speckit Review · opsmill

    Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.
    0
    installs
56. ▌
    Speckit Archive · opsmill

    Archive a feature specification into main project memory after merge, resolving gaps and conflicts
    0
    installs
57. ▌
    Speckit Auto Run · opsmill

    Run the full speckit workflow end-to-end — specify, plan, critique, tasks, implement, review, extract — making all decisions autonomously.
    0
    installs
58. ▌
    Speckit Extract Run · opsmill

    Extract knowledge, guidelines, and ADRs from one or more completed spec directories into the project documentation system.
    0
    installs
59. ▌
    Speckit Review Code · opsmill

    General code quality review — project guideline compliance, bug detection, code quality analysis.
    0
    installs
60. ▌
    Speckit Summary Run · opsmill

    Produce a flow-level summary of the current Claude Code session — executive summary, chronological timeline, and outcomes — written into the active feature directory next to spec.md / plan.md.
    0
    installs
61. ▌
    Speckit Review Tests · opsmill

    Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.
    0
    installs
62. ▌
    Speckit Review Types · opsmill

    Type design analysis — encapsulation, invariant expression, usefulness, and enforcement.
    0
    installs
63. ▌
    Speckit Iterate Apply · opsmill

    Apply a pending iteration to spec documents — update all artifacts that speckit.implement relies on, then hand off to implementation.
    0
    installs
64. ▌
    Speckit Reconcile Run · opsmill

    Reconcile implementation drift by updating the feature's own spec, plan, and tasks
    0
    installs
65. ▌
    Speckit Review Errors · opsmill

    Error handling review — silent failure detection, catch block analysis, error logging.
    0
    installs
66. ▌
    Speckit Iterate Define · opsmill

    Define an iteration on the current feature — analyze the change request against current spec state and implementation progress, then write a reviewable iteration plan.
    0
    installs
67. ▌
    Speckit Retrospect Run · opsmill

    Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.
    0
    installs
68. ▌
    Speckit Review Comments · opsmill

    Code comment accuracy verification, documentation completeness assessment, comment rot detection.
    0
    installs
69. ▌
    Speckit Review Simplify · opsmill

    Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Advisory only.
    0
    installs
70. ▌
    Speckit Checkpoint Commit · opsmill

    Commit changes at meaningful checkpoints throughout the workflow
    0
    installs
71. ▌
    Speckit Tinyspec Classify · opsmill

    Classify task complexity and recommend tinyspec or full SDD workflow
    0
    installs
72. ▌
    Speckit Tinyspec Tinyspec · opsmill

    Generate a single lightweight spec file with context, plan, and tasks for small changes
    0
    installs
73. ▌
    Speckit Tinyspec Implement · opsmill

    Implement a small change directly from its tinyspec file
    0
    installs
74. ▌
    Speckit Plan · opsmill

    Execute the implementation planning workflow using the plan template to generate design artifacts.
    0
    installs
75. ▌
    Speckit Tasks · opsmill

    Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
    0
    installs
76. ▌
    Infrahub Common · opsmill bundle

    Shared references and cross-cutting rules for all Infrahub skills — GraphQL syntax, .infrahub.yml format, and common patterns. DO NOT TRIGGER directly — loaded automatically by other Infrahub skills when they need shared references.
    0
    installs
77. ▌
    Speckit Analyze · opsmill

    Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
    0
    installs
78. ▌
    Speckit Clarify · opsmill

    Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
    0
    installs
79. ▌
    Speckit Specify · opsmill

    Create or update the feature specification from a natural language feature description.
    0
    installs
80. ▌
    Speckit Converge · opsmill

    Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
    0
    installs
81. ▌
    Speckit Checklist · opsmill

    Generate a custom checklist for the current feature based on user requirements.
    0
    installs
82. ▌
    Speckit Implement · opsmill

    Speckit Implement
    0
    installs
83. ▌
    Speckit Constitution · opsmill

    Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
    0
    installs
84. ▌
    Speckit Taskstoissues · opsmill

    Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
    0
    installs
85. ▌
    Infrahub Auditing Repo · opsmill bundle

    Audits an Infrahub repository against best practices and rules, producing a structured compliance report. TRIGGER when: reviewing repo for compliance, onboarding to existing project, pre-deployment validation, catching issues. DO NOT TRIGGER when: creating schemas, writing checks/generators, querying live data, populating objects.
    0
    installs
86. ▌
    Infrahub Analyzing Data · opsmill bundle

    Analyzes and correlates live Infrahub data via the MCP server — answers operational questions, detects drift, and investigates impact. TRIGGER when: querying infrastructure data, checking compliance, investigating change impact, producing ad-hoc reports. DO NOT TRIGGER when: writing automated checks, building transforms, designing schemas, populating data files.
    0
    installs
87. ▌
    Infrahub Managing Menus · opsmill bundle

    Creates Infrahub custom navigation menus for the web UI sidebar, organizing node types into logical groups. TRIGGER when: designing sidebar menus, grouping node types in UI, customizing Infrahub web interface navigation. DO NOT TRIGGER when: designing schemas, writing checks or transforms, populating data objects.
    0
    installs
88. ▌
    Infrahub Managing Checks · opsmill bundle

    Creates Infrahub check definitions — Python validation logic and GraphQL queries for proposed change pipelines. TRIGGER when: writing validation checks, creating Python checks, building data quality guards for proposed changes. DO NOT TRIGGER when: designing schemas, querying live data, building transforms or generators.
    0
    installs
89. ▌
    Infrahub Managing Objects · opsmill bundle

    Creates and manages Infrahub object data YAML files for populating infrastructure instances — devices, locations, organizations, and modules. TRIGGER when: creating device instances, populating data files, defining locations or organizations, adding infrastructure objects. DO NOT TRIGGER when: designing schemas, writing Python checks/generators, querying live data.
    0
    installs
90. ▌
    Infrahub Managing Schemas · opsmill bundle

    Creates, validates, and modifies Infrahub schema YAML files — nodes, generics, attributes, relationships, and extensions. TRIGGER when: designing data models, adding schema nodes, validating schema definitions, planning schema migrations. DO NOT TRIGGER when: populating data objects, writing checks/generators/transforms, querying live data.
    0
    installs
91. ▌
    Infrahub Managing Generators · opsmill bundle

    Creates Infrahub Generators — design-driven automation that builds infrastructure objects from templates and topology definitions. TRIGGER when: building design-to-implementation workflows, auto-creating objects from templates, topology-driven generation. DO NOT TRIGGER when: designing schemas, writing data transforms, querying live data, populating static data files.
    0
    installs
92. ▌
    Infrahub Managing Transforms · opsmill bundle

    Creates Infrahub transforms that convert data into JSON, text, CSV, or device configs using Python or Jinja2 templates. TRIGGER when: building config generation, data export, format conversion, Jinja2 templates, artifact pipelines. DO NOT TRIGGER when: designing schemas, writing validation checks, creating generators, querying live data.
    0
    installs
93. ▌
    Speckit Infrahub Speckit Route Plan · opsmill

    Hook command — runs before the active integration's speckit plan command in Infrahub projects. Invokes the matching infrahub-managing-* skill so Phase 0 research and data-model design are grounded in authoritative Infrahub reference material.
    0
    installs
94. ▌
    Speckit Infrahub Speckit Route Specify · opsmill

    Hook command — runs before the active integration's speckit specify command in Infrahub projects. Detects .infrahub.yml, classifies artifact type, gates skill invocation, and emits the template-override directive that the core specify skill consumes.
    0
    installs
95. ▌
    Speckit Infrahub Speckit Route Implement · opsmill

    Hook command — runs before the active integration's speckit implement command in Infrahub projects. Invokes the matching infrahub-managing-* skill for each artifact type that tasks.md touches, so implementation code follows authoritative Infrahub patterns and conventions.
    0
    installs