write-claude-tooling

Enforce token-efficient authoring rules for Claude Code configuration files.

4|Updated Apr 10, 2023
One-click install
npx skills add https://github.com/dudeofawesome/nix-config --skill write-claude-tooling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-claude-tooling
Source: https://github.com/dudeofawesome/nix-config/tree/main/modules/presets/home-manager/paciolan/llms/skills/write-claude-tooling
Command: npx skills add https://github.com/dudeofawesome/nix-config --skill write-claude-tooling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Token-efficient authoring rules for Claude Code configuration and project documentation, reducing token usage while preserving clarity.

Core Features & Use Cases

  • Enforce four publishing principles: document only what Claude doesn't know, prefer linking to code, prefer scripts for deterministic tasks, and show, don't tell.
  • Improve consistency across CLAUDE.md, AGENTS.md, SKILL.md by providing a unified authoring approach and frontmatter-driven discovery.
  • Support end-to-end workflow for Claude tooling, enabling scalable guidelines for teams with multiple skills and commands.

Quick Start

Follow the four Claude tooling principles to align CLAUDE.md, AGENTS.md, and SKILL.md with token-efficient practices.

Frequently Asked Questions about write-claude-tooling

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

FAQPage Schema
How do I write token-efficient Claude Code documentation for CLAUDE.md and SKILL.md files?

Token-efficient Claude documentation follows four principles: document only what Claude doesn't know, prefer linking to code, prefer scripts for deterministic tasks, and show, don't tell. This approach reduces token usage while preserving clarity.

What is frontmatter-driven discovery for Claude tooling and how does it work?

Frontmatter-driven discovery uses explicit metadata fields in SKILL.md files to enable scalable, consistent skill activation and unified authoring across teams managing multiple Claude commands and guidelines.

How do I keep AGENTS.md and CLAUDE.md configurations consistent across a repository?

Keep Claude configurations consistent by applying a unified authoring approach with frontmatter-driven discovery and a trigger-based activation model across CLAUDE.md, AGENTS.md, and SKILL.md files to enforce scalable team guidelines.

Does this token-efficient documentation approach support teams with multiple Claude skills?

Yes, the token-efficient authoring approach supports end-to-end workflows for Claude tooling, enabling scalable guidelines for teams managing multiple skills and commands through unified authoring and trigger-based activation.

When should I not document a process in Claude configuration files?

Avoid documenting a process in Claude configuration files if Claude already knows it, or if the task is deterministic and better handled by linking to code or using scripts rather than written explanations.