markdown-templates

Generate standardized Markdown task and test-case skeletons using variable templates.

Updated Dec 25, 2025
One-click install
npx skills add https://github.com/Zeliper/z-coder --skill markdown-templates
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: markdown-templates
Source: https://github.com/Zeliper/z-coder/tree/main/.claude/skills/markdown-templates
Command: npx skills add https://github.com/Zeliper/z-coder --skill markdown-templates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a library of formal Markdown templates to speed content creation and ensure consistency across task docs, test plans, and outputs.

Core Features & Use Cases

  • Template library: Access templates for task skeletons, test cases, agent results, and step status.
  • Variables & substitution: Understand the {{TIMESTAMP}} and {{STATUS}} style placeholders used by templates.
  • Quick Start: Read a template, substitute variables, and write the final document.

Quick Start

Read .claude/templates/task-template.md, replace the placeholder variables (e.g., {{TASK_ID}}, {{TITLE}}) with real values, and write the resulting task file to the appropriate path.

Frequently Asked Questions about markdown-templates

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

FAQPage Schema
How do I standardize Markdown documentation across multiple files and projects?

Standardize Markdown documentation by using ready-made templates stored in .claude/templates. Read templates like task-template.md, substitute {{VARIABLE}} placeholders with your content, and write the standardized output to your project. This ensures consistent formatting across task docs, test plans, and agent results.

What are Markdown template variables and how do I use them?

Markdown templates use {{VARIABLE}} placeholders like {{TIMESTAMP}}, {{STATUS}}, {{TASK_ID}}, and {{TITLE}} to mark dynamic content. Replace these placeholders with actual values specific to your task, test case, or output. The template library provides predefined structures for task skeletons, test-case formats, and step-status records.

Can I automate content generation for task skeletons and test cases?

Yes. Use template-driven generation with this Skill to automate creation of task skeletons, test-case formats, agent-result documents, and step-status records. The markdown-writer-agent workflow enables dynamic content substitution, eliminating manual formatting and reducing inconsistency across documentation.

How do I get started creating consistent documentation with templates?

Read the template file from .claude/templates, substitute the {{VARIABLE}} placeholders with your specific values (task ID, title, timestamp, status), and write the resulting Markdown file to your project directory. This three-step process—read, substitute, write—applies to all template types in the library.

What documentation problems does template standardization solve?

Markdown templating solves inconsistent documentation by enforcing uniform structure across task docs, test plans, and AI-assisted workflow outputs. Instead of manually formatting each file, templates provide pre-defined skeletons with variable placeholders, ensuring every document follows the same schema and style.