dm-pocockify

Create and refine AI agent skill definitions with precise trigger contracts.

1|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/mlesk/darkmark-skills --skill dm-pocockify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dm-pocockify
Source: https://github.com/mlesk/darkmark-skills/tree/main/skills/productivity/dm-pocockify
Command: npx skills add https://github.com/mlesk/darkmark-skills --skill dm-pocockify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agent skills often have vague trigger descriptions, unclear scope, and no verification steps, leading to inconsistent performance when loaded by AI coding agents. This skill eliminates that friction by enforcing a structured, purpose-first workflow to create or refine skills that load reliably and produce predictable, high-quality outputs.

Core Features & Use Cases

  • 4 flexible modes: Create new skills from scratch, pocockify existing skills into sharper versions, review skills without making edits, or update skills in place.
  • Trigger-first design: Ensures skills have precise load boundaries so they only activate for relevant user requests, avoiding unnecessary context bloat.
  • Guided user input: Asks one targeted question at a time with recommended answers to clarify purpose, scope, and requirements without overwhelming users.
  • Built-in validation: Includes phase gates, exit criteria, and a final self-review checklist to catch gaps before the skill is finalized.
  • Use case example: If you have a vague skill for code review that loads for unrelated requests, use this skill to sharpen its trigger, add clear exit criteria, and produce a version that only loads when the user asks to review Python backend code for security issues.

Quick Start

Use the dm-pocockify skill to create a pocockified copy of your existing 'document-summarizer' skill that only loads when the user asks to summarize legal contracts for key risk clauses.

Frequently Asked Questions about dm-pocockify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create AI agent skills that only load for relevant coding requests?

Creating AI agent skills that load reliably requires a trigger-first design with precise load boundaries. This skill provides a structured workflow to define explicit trigger contracts so skills activate only for relevant user requests, avoiding context bloat.

What is the best way to refine vague agent skill definitions for coding agents?

Refining vague agent skill definitions involves enforcing phase gates, one-question-at-a-time user input, and a self-review checklist. This workflow sharpens existing skills into versions with clear exit criteria and predictable outputs for coding agents like Claude Code, Codex, and GitHub Copilot.

How do I review AI agent skills without making direct edits?

Reviewing AI agent skills without editing is supported by a dedicated review mode. This mode evaluates existing skill configurations against phase gates and exit criteria to identify gaps and vague trigger boundaries, producing a validation report instead of modifying the original skill.

Why does my coding agent skill load for unrelated user requests?

Coding agent skills load for unrelated requests due to vague trigger descriptions and unclear scope. Applying a trigger-first design with explicit load boundaries ensures the skill only activates when specific user conditions are met, such as reviewing Python backend code for security issues.

Can I use this skill creation workflow for GitHub Copilot and Claude Code?

Yes, this skill creation workflow applies to building skills for AI coding agents like Claude Code, Codex, and GitHub Copilot. It ensures skills have precise load boundaries and produce predictable outputs across these platforms.

What are the limitations of designing agent skills without phase gates?

Designing agent skills without phase gates leads to inconsistent performance and unreliable skill configurations. Without built-in validation and exit criteria, skills lack the necessary structure to catch gaps before finalization, resulting in vague and unpredictable outputs.