agent-authoring

Creates and refactors offline Claude Code agent files with bounded tool access.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/ririnto/sinon --skill agent-authoring-ririnto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-authoring
Source: https://github.com/ririnto/sinon/tree/main/plugins/agent-capability-kit/skills/agent-authoring
Command: npx skills add https://github.com/ririnto/sinon --skill agent-authoring-ririnto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and maintain clear, self-contained Claude Code agent files with explicit triggers, bounded tool access, and robust system prompts to enable autonomous execution offline.

Core Features & Use Cases

  • Ensure one clearly scoped agent per file with well-defined responsibilities.
  • Enforce imperative trigger language, bounded tool surfaces, and a self-contained workflow.
  • Support offline authoring and consistent frontmatter and body structure across repository agents.

Quick Start

Write a new agent file named data-validator.md that enforces a bounded tool surface and explicit output shape, suitable for offline authoring.

Frequently Asked Questions about agent-authoring

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

FAQPage Schema
How do I author Claude Code agents with bounded tool access?

You author Claude Code agents by defining clear triggers, bounded tool surfaces, and robust system prompts in a self-contained file. This ensures safe autonomous execution offline by enforcing explicit output shapes and role boundaries.

What is the best way to structure frontmatter for Claude Code agents?

The best way to structure frontmatter for Claude Code agents is to use a minimal, self-contained workflow that enforces required metadata and body structure. This guarantees one clearly scoped agent per file with well-defined responsibilities.

How do I enforce a single well-scoped agent per file?

To enforce a single well-scoped agent per file, you must use imperative trigger language and bounded tool access. This approach maintains explicit role boundaries and prevents reliance on external prompts during offline authoring.

Can I refactor existing agent files to have explicit output shapes offline?

Yes, you can refactor agent files offline to ensure explicit output shapes. By enforcing frontmatter requirements and a self-contained workflow, you maintain consistent agent structure and robust system prompts without external dependencies.

Why does my Claude Code agent rely on external prompts during execution?

Claude Code agents rely on external prompts if they lack a self-contained workflow and robust system prompts. Authoring agents with explicit triggers and bounded tool access eliminates this dependency, enabling autonomous offline execution.