Template Builder logo

Template Builder

Organization
Community-Access
template-builder

Build GitHub issue, PR and discussion templates from a guided wizard.

Overview

PublisherCommunity-Access
Repositoryaccessibility-agents
Skill nametemplate-builder
Stars
429
Forks
51
Bundled files
3
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Community-Access on GitHub. Read the source before you install it.

Installation

Install the Template Builder AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Community-Access/accessibility-agents/tree/main/skills/template-builder
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git /tmp/accessibility-agents
mkdir -p .claude/skills
cp -r /tmp/accessibility-agents/skills/template-builder .claude/skills/template-builder
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Template Builder in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Template Builder on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Template Builder is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Template Builder Agent

Shared instructions

Skills: github-workflow-standards, github-scanning

A magical interactive agent that guides you through building GitHub issue templates step-by-step using VS Code's Ask Questions feature. Instead of writing YAML, answer simple questions and the agent generates the template for you.

How to Use

In VS Code

  1. Open Copilot Chat (Ctrl+Shift+I Windows, Cmd+Shift+I macOS)
  2. Type: @template-builder or /build-template
  3. The agent will ask you a series of questions to understand your template
  4. Answer each question in the Ask Questions prompts
  5. The agent generates your complete YAML template
  6. Copy the output to .github/ISSUE_TEMPLATE/your-template-name.yml

In GitHub Web

  1. Open Copilot Chat (Copilot button in top right)
  2. Mention: @template-builder
  3. Type your template goals (e.g., "I want to build an accessibility bug report template")
  4. The agent provides step-by-step YAML scaffolding you can copy and refine

Example Workflow

You: @template-builder create accessibility bug template

Agent asks (via Ask Questions):

  1. Template name? -> You answer: "Accessibility Bug Report"
  2. What's this template for? -> "Report screen reader and keyboard issues"
  3. First field? -> "Screen Reader (dropdown)"
  4. Dropdown options? -> "NVDA, JAWS, VoiceOver, Other"
  5. Is it required? -> "Yes"
  6. Next field? -> "Browser (dropdown)" ... (continues for each field)

Agent outputs: Complete YAML template ready to paste


Pre-Built Workflow: Guided Accessibility Template

The agent includes a guided workflow for the most common case: building an accessibility bug report template.

Invoke with

  • @template-builder + "create accessibility template"
  • /build-a11y-template

Workflow

The agent skips to Phase 2 but pre-populates it with accessibility-specific fields:

  1. Component affected? (dropdown with agent names)
  2. Screen reader (with NVDA, JAWS, VoiceOver, TalkBack, etc. pre-options)
  3. Browser version
  4. Operating system
  5. Expected behavior vs actual behavior
  6. Steps to reproduce
  7. WCAG success criterion (dropdown with criteria)
  8. Before submitting checklist (checkboxes for verification)

Output: Production-ready accessibility bug template you can immediately use.


Advanced: Customize the Template Builder

The Template Builder agent itself can be extended. Students in the workshop can:

  1. Add new field types -> Extend the agent to support custom validations
  2. Create workflow templates -> Pre-built templates for specific issue types (Security, Documentation, etc.)
  3. Add conditional fields -> Show/hide fields based on previous answers
  4. Export to markdown -> Generate Markdown templates in addition to YAML
  5. Template sharing -> Generate a code block to share with other projects

Integration with Nexus

The Template Builder works alongside the five core agents:

AgentCreatesTemplate Builder Uses
@daily-briefingIssue summariesTemplates to collect consistent data
@issue-trackerIssue recommendationsTemplates to standardize issue quality
@pr-reviewPR checklistsTemplates to structure PR descriptions
@analyticsPerformance insightsTemplates to capture metrics consistently
@template-builderIssue templates themselves(This agent)

Together: The five agents automate workflow; the Template Builder automates the infrastructure that makes workflows possible.


Day 2 Amplifier: From Manual to Magical

Each day 1, with its day 2 in browser, day 2 in VS code and nexus.

Day 1Day 2 in BrowserDay 2 in VS CodeNexus
Learn to identify accessibility issues in code reviewLearn to design templates that prevent those issuesUse Template Builder to generate templates interactivelyAgent automates the entire cycle
(Chapter 14)(Chapter 15)(Chapter 16)(Capstone)

Behavioral Rules

  1. Check workspace context first. Look for scan config files (.a11y-*-config.json) and previous audit reports in the workspace root.
  2. Wizard mode is the default. Always start with guided questions via Ask Questions rather than generating a template cold.
  3. Never overwrite existing templates without confirming. Check for existing files in .github/ISSUE_TEMPLATE/ first.
  4. YAML form format always. Never generate Markdown-style issue templates (the legacy format).
  5. Always include config.yml. Every template set needs a chooser config alongside the templates.
  6. Preview before saving. Show the generated YAML to the user before writing to disk.
  7. Validate field IDs. YAML id fields must be lowercase, hyphenated, no spaces - enforce this silently.
  8. Accessibility defaults. All templates include a clear title format, description, and at minimum one structured text area.
  9. Offer all three formats. After building an issue template, offer to also build a PR template and discussion template.
  10. Link to related agents. After creation, offer to immediately use the template via @issue-tracker or run a community health check via @contributions-hub.

Reference files

Read one only when the task reaches it. Do not read them all up front.

  • references/template-builder-guide-step-by-step.md - Template Builder Guide: Step-by-Step
  • references/hands-on-exercise-build-your-own-template-builde.md - Hands-On Exercise: Build Your Own Template Builder, Technical Details: VS Code Ask Questions...

Output contract

Produce the file or script the task asks for. Report what you wrote as a short list of paths and what each one changes. Do not restate the file contents.

Shared rules, dispatch contract and schemas: skills/a11y-core/SKILL.md. Authoritative specifications for this skill: skills/a11y-core/references/sources.md.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Template Builder AI skill do?

Build GitHub issue, PR and discussion templates from a guided wizard.

Why use Template Builder on TypingMind?

Because you install it once and use it with any model. Template Builder is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Template Builder in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Community-Access/accessibility-agents/tree/main/skills/template-builder. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Template Builder?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Template Builder?

As many as you like. As long as a model supports skills, you can use Template Builder with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Template Builder AI skill free?

Yes. It is published on GitHub by Community-Access under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇