OpenClaw Design Audit
openclaw/clawhub
Audits OpenClaw frontend code and rendered pages for token misuse, reimplemented primitives, accessibility and responsive defects and off-brand copy, with an evidence-based report.
Build GitHub issue, PR and discussion templates from a guided wizard.
Install Template Builder
$ npx skills add Community-Access/accessibility-agents --skill template-builder -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Community-Access/accessibility-agents template-builder --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/template-builder .claude/skills/template-builder && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "template-builder" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/template-builder into .claude/skills/template-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "template-builder", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Community-Access/accessibility-agents/tree/main/skills/template-builderType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Community-Access/accessibility-agents --skill template-builder -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Community-Access/accessibility-agents template-builder --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/template-builder .agents/skills/template-builder && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "template-builder" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/template-builder into .agents/skills/template-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "template-builder", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Community-Access/accessibility-agents --skill template-builder -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Community-Access/accessibility-agents template-builder --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/template-builder .cursor/skills/template-builder && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "template-builder" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/template-builder into .cursor/skills/template-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "template-builder", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Community-Access/accessibility-agents.git --path skills/template-builder--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Community-Access/accessibility-agents --skill template-builder -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Community-Access/accessibility-agents template-builder --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/template-builder .gemini/skills/template-builder && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "template-builder" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/template-builder into .gemini/skills/template-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "template-builder", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Community-Access/accessibility-agents template-builderInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Community-Access/accessibility-agents --skill template-builder -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/template-builder .github/skills/template-builder && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "template-builder" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/template-builder into .github/skills/template-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "template-builder", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Community-Access/accessibility-agents --skill template-builder -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Community-Access/accessibility-agents template-builder --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/template-builder .opencode/skills/template-builder && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "template-builder" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/template-builder into .opencode/skills/template-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "template-builder", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
template-builder- GitHub stars
- 421
- Token cost
- ~1.6k tokens
- SKILL.md length
- 777 words
- Files
- 4 (incl. references)
- Skills in repo
- 108
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build GitHub issue, PR and discussion templates from a guided wizard.
- Works in 6 steps: Open Copilot Chat (Ctrl+Shift+I Windows,… → Type: @template-builder or /build-template → The agent will ask you a series of… → …
- Tasks that involve Accessibility
- SKILL.md covers Template Builder Agent, How to Use, Example Workflow and Pre-Built Workflow: Guided…, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Template Builder is an agent skill from Community-Access/accessibility-agents. Build GitHub issue, PR and discussion templates from a guided wizard.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `agents/openai.yaml`, `references/hands-on-exercise-build-your-own-template-builde.md` and `references/template-builder-guide-step-by-step.md`).
It sits in Frontend & Design, covering Accessibility. It works with GitHub. The repository describes itself as: Accessibility review agents for Claude Code, GitHub Copilot, and Claude Desktop. Eleven specialists that enforce WCAG 2.2 AA compliance so AI coding tools stop generating… The licence is MIT.
When your agent uses it
- Tasks that involve Accessibility
Example prompts
- “/template-builder”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Open Copilot Chat (Ctrl+Shift+I Windows, Cmd+Shift+I macOS)
- Type: @template-builder or /build-template
- The agent will ask you a series of questions to understand your template
- Answer each question in the Ask Questions prompts
- The agent generates your complete YAML template
- Copy the output to .github/ISSUE_TEMPLATE/your-template-name.yml
What it can do on your machine
Read from SKILL.md and the folder at commit decf6ba. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Template Builder loads about 1.6k tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 22 tokens; SKILL.md has 777 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Community-Access/accessibility-agents at commit decf6ba, republished under its MIT licence (© Community-Access). 777 words, ~1,593 tokens.
Download SKILL.mdSave it as
.claude/skills/template-builder/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- template-builder
- description
- Build GitHub issue, PR and discussion templates from a guided wizard.
- license
- MIT
- disable-model-invocation
- true
- metadata.tier
- specialist
- metadata.domain
- github
- metadata.output
- artifact
- metadata.effort
- medium
- metadata.title
- Template Builder
Template Builder Agent
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
- Open Copilot Chat (
Ctrl+Shift+IWindows,Cmd+Shift+ImacOS) - Type:
@template-builderor/build-template - The agent will ask you a series of questions to understand your template
- Answer each question in the Ask Questions prompts
- The agent generates your complete YAML template
- Copy the output to
.github/ISSUE_TEMPLATE/your-template-name.yml
In GitHub Web
- Open Copilot Chat (Copilot button in top right)
- Mention:
@template-builder - Type your template goals (e.g., "I want to build an accessibility bug report template")
- 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):
- Template name? -> You answer: "Accessibility Bug Report"
- What's this template for? -> "Report screen reader and keyboard issues"
- First field? -> "Screen Reader (dropdown)"
- Dropdown options? -> "NVDA, JAWS, VoiceOver, Other"
- Is it required? -> "Yes"
- 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:
- Component affected? (dropdown with agent names)
- Screen reader (with NVDA, JAWS, VoiceOver, TalkBack, etc. pre-options)
- Browser version
- Operating system
- Expected behavior vs actual behavior
- Steps to reproduce
- WCAG success criterion (dropdown with criteria)
- 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:
- Add new field types -> Extend the agent to support custom validations
- Create workflow templates -> Pre-built templates for specific issue types (Security, Documentation, etc.)
- Add conditional fields -> Show/hide fields based on previous answers
- Export to markdown -> Generate Markdown templates in addition to YAML
- Template sharing -> Generate a code block to share with other projects
Integration with Nexus
The Template Builder works alongside the five core agents:
| Agent | Creates | Template Builder Uses |
|---|---|---|
| @daily-briefing | Issue summaries | Templates to collect consistent data |
| @issue-tracker | Issue recommendations | Templates to standardize issue quality |
| @pr-review | PR checklists | Templates to structure PR descriptions |
| @analytics | Performance insights | Templates to capture metrics consistently |
| @template-builder | Issue templates themselves | (This agent) |
Together: The five agents automate workflow; the Template Builder automates the infrastructure that makes workflows possible.
Show full SKILL.md (325 more words)Show less
Day 2 Amplifier: From Manual to Magical
Each day 1, with its day 2 in browser, day 2 in VS code and nexus.
| Day 1 | Day 2 in Browser | Day 2 in VS Code | Nexus |
|---|---|---|---|
| Learn to identify accessibility issues in code review | Learn to design templates that prevent those issues | Use Template Builder to generate templates interactively | Agent automates the entire cycle |
| (Chapter 14) | (Chapter 15) | (Chapter 16) | (Capstone) |
Behavioral Rules
- Check workspace context first. Look for scan config files (
.a11y-*-config.json) and previous audit reports in the workspace root. - Wizard mode is the default. Always start with guided questions via Ask Questions rather than generating a template cold.
- Never overwrite existing templates without confirming. Check for existing files in
.github/ISSUE_TEMPLATE/first. - YAML form format always. Never generate Markdown-style issue templates (the legacy format).
- Always include
config.yml. Every template set needs a chooser config alongside the templates. - Preview before saving. Show the generated YAML to the user before writing to disk.
- Validate field IDs. YAML
idfields must be lowercase, hyphenated, no spaces - enforce this silently. - Accessibility defaults. All templates include a clear title format, description, and at minimum one structured text area.
- Offer all three formats. After building an issue template, offer to also build a PR template and discussion template.
- Link to related agents. After creation, offer to immediately use the template via
@issue-trackeror 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-Stepreferences/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.
© Community-Access, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in skills/template-builder of Community-Access/accessibility-agents.
- SKILL.md
- agents/openai.yaml
- references/hands-on-exercise-build-your-own-template-builde.md
- references/template-builder-guide-step-by-step.md
Open the folder on GitHubat commit decf6ba
Compare with similar skills
Template Builder next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Template Builder this skillCommunity-Access/accessibility-agents | 421 | — | ~1.6k | Automated safety check: Pass | MIT | |
| OpenClaw Design Auditopenclaw/clawhub | 9.5k | — | ~498 | Automated safety check: Pass | MIT | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 98 repos | ~308 | Automated safety check: Pass | None | |
| Accessibility Reviewmarkmead/hyperui | 12k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Web Animation DesignbaptisteArno/typebot.io | 11k | 2 repos | ~2.7k | Automated safety check: Pass | Custom licence | |
| Accessibility Fixeribelick/ui-skills | 9.4k | 4 repos | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
- Official
Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
Accessibility Review
markmead/hyperui
Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.
Web Animation Design
baptisteArno/typebot.io
Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.
Accessibility Fixer
ibelick/ui-skills
Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.
Wcag Audit Patterns
vmDeshpande/ai-agent-automation
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.
More from Community-Access/accessibility-agents
All 108 skills in this repoA11y Core
Community-Access/accessibility-agents
Shared contract for the Accessibility Agents skills - dispatch, findings schema, report rules.
Kb Web Scanning
Community-Access/accessibility-agents
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.
Accessibility Lead
Community-Access/accessibility-agents
Web UI accessibility lead. An agent skill from Community-Access/accessibility-agents.
Alt Text Headings
Community-Access/accessibility-agents
Alt text, SVGs, figures, charts, heading order, page titles and landmarks.
Aria Specialist
Community-Access/accessibility-agents
ARIA roles, states and properties for custom widgets and dynamic content.
Cognitive Accessibility
Community-Access/accessibility-agents
Plain language, WCAG 2.2 cognitive criteria, COGA guidance and auth UX.
Related
Works with
Categories
Questions about Template Builder
What does Template Builder do?
Build GitHub issue, PR and discussion templates from a guided wizard. Template Builder is an agent skill from Community-Access/accessibility-agents. Build GitHub issue, PR and discussion templates from a guided wizard.
When should I use Template Builder?
Template Builder fits situations like: tasks that involve Accessibility.
How do I install Template Builder in Claude Code?
Run `npx skills add Community-Access/accessibility-agents --skill template-builder -a claude-code`. Or copy the skill folder (skills/template-builder in Community-Access/accessibility-agents) into .claude/skills/template-builder in your project. Claude Code loads it when a task matches its description.
How do I install Template Builder in Codex?
Run `npx skills add Community-Access/accessibility-agents --skill template-builder -a codex`. Or copy the skill folder (skills/template-builder in Community-Access/accessibility-agents) into .agents/skills/template-builder in your project. Codex loads it when a task matches its description.
Can I use Template Builder in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Community-Access/accessibility-agents --skill template-builder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/template-builder, .gemini/skills/template-builder, .github/skills/template-builder and .opencode/skills/template-builder in your project.
What does Template Builder need to run?
SKILL.md names no scripts, command-line tools or credentials: Template Builder is instructions for the agent only.
Does Template Builder access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Template Builder safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Template Builder use?
Template Builder is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Template Builder use?
About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.7k tokens, read only when the agent opens those files.
What are the alternatives to Template Builder?
Skills that share tags, products or a category with Template Builder: OpenClaw Design Audit (openclaw/clawhub, 9.5k stars), Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars), Accessibility Review (markmead/hyperui, 12k stars) and Web Animation Design (baptisteArno/typebot.io, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Template Builder?
Community-Access (a GitHub organization) maintains it in Community-Access/accessibility-agents, which has 421 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on September 23, 2026.
Source: Community-Access/accessibility-agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.