tda-skill-authoring-workbench

Guides authoring and syncing of agent skills across dual-tree Claude Code and Codex layouts.

1|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/ZK-Theory/TDL --skill tda-skill-authoring-workbench-zk-theory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tda-skill-authoring-workbench
Source: https://github.com/ZK-Theory/TDL/tree/main/.agents/skills/tda-skill-authoring-workbench
Command: npx skills add https://github.com/ZK-Theory/TDL --skill tda-skill-authoring-workbench-zk-theory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating or modifying agent skills in this repository is error-prone because skills live in a dual-tree layout: the .agents tree is the authoring source of truth, byte-mirrored into the .claude tree by a sync tool. Editing the wrong tree, forgetting to register a skill in the sync manifest, or writing workflow-summarizing descriptions causes sync failures and degraded agent behavior. ## Core Features & Use Cases - Dual-Tree Authoring Procedure: Enforces authoring in the .agents tree, registering skills in SYNC_SKILLS, and verifying byte-identical mirrors with the sync tool's --check mode. - Skill Design Decisions: Provides a checklist for tier classification (core/specialist/optional), trigger-only description style, output schemas, self-test prompts, and overlap resolution with existing skills. - House Style & Guardrails: Defines frontmatter conventions, body structure (boundary intro, procedure, escalation rules), and a completion checklist. - Use Case: When adding a new skill for a recurring task, follow this workbench to decide its tier, write a trigger-only description, register it in the sync manifest, and confirm both trees match before committing. ## Quick Start Ask the agent to help author a new skill for the repository and walk through the tier classification, description style, and sync registration steps.

Frequently Asked Questions about tda-skill-authoring-workbench

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

FAQPage Schema
How do I add a new agent skill to a dual-tree Claude Code repository?

Author the skill in the .agents tree, register it in SYNC_SKILLS in tools/sync_agent_skills.py, then run the sync tool and its --check mode. Both trees must be byte-identical before committing.

How should I write a skill description for agent discovery?

Write a trigger-only, third-person description starting with "Use when". Never summarize the workflow, because agents will follow a summarized description instead of reading the skill body.

What happens if I edit the .claude mirror tree directly?

Edits to the .claude mirror are overwritten at the next sync, or can reverse a newer fix. All changes must be applied to the .agents authoring tree and propagated via the sync tool.

Why does the skill sync fail after adding a new skill?

The sync fails when a new skill is not registered in SYNC_SKILLS in tools/sync_agent_skills.py. Classification is fail-safe, so an unregistered skill hard-errors every sync run until registered or explicitly excluded.

When should a task not become a skill?

Avoid creating a skill when it duplicates or overlaps an existing one, or when two skills already split the territory. Resolve by boundary statements in both directions, or propose a merge instead of adding a third skill.