write-agent

Create new project-specific agents with standardized structure and deduplication checks.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/dain-agency/mood-tracker --skill write-agent-dain-agency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-agent
Source: https://github.com/dain-agency/mood-tracker/tree/main/.claude/skills/write-agent
Command: npx skills add https://github.com/dain-agency/mood-tracker --skill write-agent-dain-agency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of creating bloated, duplicative, or inconsistent specialized agents that waste context window space and fragment project knowledge and conventions.

Core Features & Use Cases

  • Justification & Deduplication Checks: Ensures new agents are necessary and don't overlap with existing ones, avoiding redundant context usage.
  • Standardized Structure Enforcement: Automatically applies the project's required frontmatter, body skeleton, length limits, and tool constraints for all new agents.
  • Context Bloat Prevention: Guides authors to link to existing project rules instead of restating them, keeping agent files lean and maintainable.
  • Use Case: When a user requests a new agent for automated API endpoint testing, this Skill ensures it follows the project's existing agent patterns, doesn't duplicate the existing typescript-fixer agent, and includes only the required tools and verification steps.

Quick Start

Use the write-agent skill to create a new specialized agent for automated Slack message formatting that adheres to the project's existing agent conventions.

Frequently Asked Questions about write-agent

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

FAQPage Schema
How do I prevent duplicative specialized agents from wasting context window space?

To prevent duplicative agents from wasting context window space, enforce justification and deduplication checks before authoring new agents, ensuring they do not overlap with existing project patterns and conventions.

What is the best way to maintain context efficiency when authoring project-specific agents?

Context efficiency for project-specific agents is maintained by linking to existing project rule files instead of restating content, keeping agent files lean and enforcing strict length discipline and scope boundaries.

How do I enforce standardized frontmatter and tool constraints for new specialized agents?

You can enforce standardized frontmatter, body skeletons, length limits, and tool constraints for new specialized agents by applying an automated structure enforcement process during agent authoring.

Does this agent authoring approach work for mechanical fixers and code reviewers?

Yes, this agent authoring approach works for mechanical fixers and code reviewers by ensuring all new project-specific agents align with existing agent patterns and project conventions without duplicating functionality.

Why do my specialized agents fragment project knowledge and conventions?

Specialized agents fragment project knowledge and conventions when they are authored without standardized structures, leading to bloated, duplicative, or inconsistent context that diverges from existing project rules.

Can I create a new agent for automated API endpoint testing without duplicating existing fixers?

Yes, you can create an agent for automated API endpoint testing without duplicating existing fixers by running deduplication checks to ensure the new agent includes only required tools and verification steps.