content-template-gateway

Routes structured content authoring through researched templates with enforced directives.

1|1|Updated May 24, 2026
One-click install
npx skills add https://github.com/bm629/agent-skills --skill content-template-gateway-bm629
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-template-gateway
Source: https://github.com/bm629/agent-skills/tree/main/skills/content-template-gateway
Command: npx skills add https://github.com/bm629/agent-skills --skill content-template-gateway-bm629

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents and users frequently author structured documents (RFCs, ADRs, PRDs, runbooks, PR descriptions, tickets) from scratch, producing inconsistent formats and missing sections. This Skill acts as a mandatory gate that identifies the content type, checks for an existing template, forges one via research if missing, and returns it with a hard-refusal directive so every artifact follows a canonical structure. ## Core Features & Use Cases - Identify and route: Researches the user's intent to determine content-type and variant slugs, then checks docs/templates/<content-type>/<variant>/ for an existing template. - Template forging: When no template exists, it researches canonical structures from official references and corroborating sources, then writes template.md, research.md, and a variant index README.md. - Enforcement directive: Returns an ASCII-bounded directive requiring the caller to author content into the template before any destination action (file write, gh pr create, Jira ticket, Slack post). - Use Case: Before running gh pr create for an auth refactor, the agent invokes this Skill, receives the PR-description template plus directive, fills it in, and only then creates the PR. ## Quick Start Ask the agent to use content-template-gateway before writing a runbook for restarting the API, and follow the returned template directive.

Frequently Asked Questions about content-template-gateway

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

FAQPage Schema
How do I enforce templates for agent-authored documents?

Invoke content-template-gateway before any authoring action. It identifies the content type, checks docs/templates for an existing template, and returns it with a hard-refusal directive requiring the agent to fill the template before writing files or calling destination APIs.

What content types does the template gateway support?

It supports any structurally templated shape: RFC, ADR, post-mortem, runbook, spec, plan, PRD, README, release notes, retrospective, PR and issue bodies, Jira or Linear tickets, multi-paragraph commit messages, and Slack or email announcements.

Does the template gateway work without a research skill installed?

Yes. The skill is self-contained and falls back to built-in WebSearch and WebFetch when no research-capable skill is available. It prefers a deep-research skill when present but never declares a hard dependency.

What happens when a template folder is incomplete or orphaned?

Phase B detects orphan folders missing template.md, research.md, or forge frontmatter and prompts the user to regenerate, delete, or skip the folder. After the choice, it re-classifies the folder and continues the normal workflow.

When should I not use the content template gateway?

Skip it for single-line or trivial content like one-line commit messages or terse replies, for editing existing documents, for filling templates with real content, and for project scaffolding tasks. It governs new structured multi-section authoring only.