AI Agent Workflow Collection

Detects task agent, complexity tier, and model automatically at Phase 0 orient. Invoked first in every workflow. NOT for runtime agent routing inside a single skill (see orchestration-rules.md).

Use when answering factual or explanatory questions about the current project — codebase, architecture, conventions, workflows, constraints — with minimal cited evidence. Triggers on "how does X work here", "what does X mean", "why is X structured this way", "is this claim true in the repo", "explain X with sources". NOT for brainstorming or comparing approaches (mk:brainstorming), trade-off decisions (mk:party), debugging/root cause (mk:investigate), code review (mk:review), plans (mk:plan-creator), security audits (mk:cso), visual explanations/diagrams (mk:preview --explain), test-coverage gaps (mk:nyquist), library docs (mk:docs-finder), or workflow navigation (mk:help).

Use when copy-catting, replicating, or adapting features from external systems, repos, apps, or ideas into the current project. Triggers on 'copy this from', 'replicate', 'clone this feature', 'how does X do Y', 'chom', 'like how X does it', 'port from', 'build like', '1:1 copy'. NOT for packing the current project (see mk:pack); NOT for one-shot URL-to-markdown fetches (see mk:web-to-markdown).

Target a specific Google Chrome user profile for browser automation via CDP. Discovers installed profiles from the Chrome Local State file, launches Chrome with the requested profile attached to a debug port, and connects agent-browser via agent-browser connect . Use when "automate using my Work/Personal Chrome", "open site with my saved session", or "use Chrome profile named ". NOT for headless scraping without an existing user profile (use mk:agent-browser directly); NOT for importing cookies only (use agent-browser --auto-connect state save).

Bulk Confluence operations on 10+ pages via the confluence-as wrapper: bulk-label / bulk-move / bulk-delete. Dry-run is MANDATORY first. Triggers: ''bulk update N pages'', ''mass label'', ''delete all pages matching CQL'', ''bulk-move pages to PARENT''. NOT for single-page ops (mk:confluence-page); NOT for comment/attachment ops (mk:confluence-collaborate).

Manage Confluence collaboration surface via the confluence-as wrapper: comments, attachments, labels, watchers. Triggers: ''add comment to page 12345'', ''upload attachment to page 12345'', ''label page 12345 as urgent'', ''watch page 12345''. Inline-vs-footer comment safety enforced. NOT for page CRUD (mk:confluence-page); NOT for bulk ops (mk:confluence-bulk).

Confluence page CRUD via the confluence-as wrapper. Triggers: ''create page in SPACE'', ''show me page 12345'', ''update title of page 12345'', ''delete page 12345'', ''page hierarchy under 12345'', ''copy page 12345 to SPACE''. NOT for bulk ops on 10+ pages (mk:confluence-bulk); NOT for spec analysis (mk:confluence-spec-analyst); NOT for comments/attachments/labels (mk:confluence-collaborate).

Confluence CQL search + space list + saved-filter + export via the confluence-as wrapper. Triggers: ''search confluence'', ''find pages where X'', ''cql for ...'', ''export search results'', ''list spaces'', ''manage saved filters''. CQL injection-safe via the shared sanitizer. NOT for single-page CRUD (mk:confluence-page); NOT for bulk write ops (mk:confluence-bulk).

Deep spec analysis on a Confluence page. Reads page (+ children) via the confluence-as wrapper, produces a structured Spec Research Report with requirements, acceptance criteria, gaps, ambiguities, and suggested user stories for human review. Read-only — does NOT create Jira tickets. Triggers: ''analyze spec for PAGE-ID'', ''extract requirements from confluence page'', ''spec research on URL''. NOT for raw page CRUD (mk:confluence-page); NOT for ticket complexity scoring (mk:planning-engine).

Retrieve up-to-date library, framework, and project documentation using scripts + MCP tools (Context7, Context Hub) with intelligent fallback. Use this skill whenever the user or agent needs documentation for any library, framework, API, SDK, or internal project spec. Triggers on "docs for [X]", "how does [library] work", "find documentation", "API reference for", "look up [feature] in [library]", "latest docs", "what's the API for", "find our [internal spec]", or any request that requires current, accurate documentation rather than relying on training data. Always prefer this skill over raw WebSearch for documentation retrieval — it returns structured, context-efficient results.

GitHub project management via the gh CLI — create and triage issues, manage GitHub Projects v2 boards (add items, update status fields), manage labels and milestones, and generate handoff-status summaries. Use when "create a GitHub issue", "add to project board", "update sprint status", "create label/milestone", or "give me a handoff summary of open work". NOT for code review (see mk:review-pr); NOT for PR creation (see mk:ship); NOT for git operations (see mk:ship / mk:resolving-merge-conflicts).

Use when transforming existing code into agent-consumable surfaces — CLI (npm-publishable), MCP server (stdio/SSE/Streamable HTTP), and a companion skill. Triggers on 'agentize', 'henshin', 'expose as MCP', 'wrap as CLI', 'publish to npm', 'make LLM-accessible', 'turn into agent tool', 'expose feature as tool'. Runs when the user has existing code and wants to ship it to agents. NOT for building new code from scratch (see mk:bootstrap); NOT for reviewing or verifying existing code (see mk:review).

Render an HTML/CSS/JS template to a local MP4 video by capturing frames with headless Chromium (via Playwright) and encoding them with ffmpeg. Use when "render my animation as a video", "export HTML to MP4", "make a video from my web template", or "capture CSS animation as MP4". NOT for recording live browser interactions (use agent-browser record start); NOT for screen recording; NOT for AI video generation (use mk:multimodal).

JIRA project / user / group / scheme / automation administration via the jira-as wrapper (11 sub-domains, ~65 verbs). Triggers: ''create JIRA project'', ''list users'', ''delete user USERNAME'', ''list permission schemes'', ''create group NAME''. Requires admin role. Destructive ops (project/user/group delete) require 2-step token confirmation. NOT for per-issue ops (mk:jira-issue / mk:jira-lifecycle); NOT for JSM admin (mk:jira-jsm).

Full Jira ticket context analysis via the jira-analyst agent — including media (attached images / PDFs / screenshots) and linked issues. Produces structured findings suitable for posting back as a Jira comment. Read-only. Triggers: ''analyze KEY'', ''rca for KEY'', ''describe KEY with media''. NOT for complexity scoring (mk:jira-evaluator); NOT for story-point estimation (mk:jira-estimator).

Bulk JIRA operations on 10+ issues via the jira-as wrapper: bulk transition / assign / set-priority / clone / delete. Dry-run is MANDATORY first. Triggers: ''bulk update N issues'', ''mass transition'', ''transition 50+ issues to Done'', ''bulk-clone'', ''bulk-delete''. NOT for single-issue ops (mk:jira-issue / mk:jira-lifecycle).

Manage JIRA collaboration surface via the jira-as wrapper: comments, attachments, watchers, notify. Triggers: ''comment on KEY'', ''add attachment to KEY'', ''watch KEY'', ''notify KEY watchers''. Internal-vs-public comment safety enforced. NOT for issue CRUD (mk:jira-issue); NOT for issue links (mk:jira-relationships).

Generate developer artifacts from Jira tickets via the jira-as wrapper: branch names, PR descriptions, parsed commits, commit/PR-to-issue links. Triggers: ''branch name for KEY'', ''PR description for KEY'', ''parse commits for issue keys'', ''link PR to KEY''. NOT for executing git/gh commands directly (mk:ship); NOT for issue CRUD (mk:jira-issue).

Heuristic story-point estimation for a single Jira ticket via the jira-estimator agent. Read-only. Triggers: ''estimate KEY'', ''story points for KEY'', ''how complex is KEY''. NOT for complexity-only analysis (mk:jira-evaluator); NOT for full RCA (mk:jira-analyst).

Evaluate Jira ticket complexity + inconsistencies via the jira-evaluator agent. Read-only. Triggers: ''evaluate KEY'', ''analyze ticket complexity for KEY'', ''check ticket quality for KEY''. NOT for estimation (mk:jira-estimator); NOT for full RCA (mk:jira-analyst).

JIRA custom field discovery + configuration via the jira-as wrapper. Triggers: ''field ID for X'', ''list custom fields'', ''check fields for project PROJ'', ''configure agile fields for board''. Read ops are open; create/configure-agile require admin. NOT for setting per-issue field values (mk:jira-issue update).

JIRA Service Management via the jira-as wrapper: service desks, request types, requests, customers, organizations, queues, SLAs, approvals (8 sub-domains). Triggers: ''create JSM request'', ''list service desks'', ''SLA status for KEY'', ''approve request KEY'', ''list queue NAME''. Requires JSM-licensed tenant + agent role. NOT for core Jira issue ops (mk:jira-issue); NOT for project admin (mk:jira-admin).

JIRA-side cache + project-context discovery via the jira-as wrapper. Triggers: ''jira cache status'', ''clear jira cache'', ''discover project context for PROJ''. Diagnostic-only — no Atlassian state changes. NOT for issue CRUD; NOT for project admin (mk:jira-admin).

Manage JIRA issue relationships via the jira-as wrapper: link, unlink, blockers, dependencies, clone, bulk-link. Triggers: ''link KEY blocks KEY'', ''what blocks KEY'', ''clone KEY'', ''unlink KEY from KEY''. NOT for sprint/epic relationships (mk:jira-agile).