agent-artifacts

Route agent-generated artifacts to docs/.claude/ subdirectories.

Updated Jan 7, 2026
One-click install
npx skills add https://github.com/fyrsmithlabs/marketplace --skill agent-artifacts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-artifacts
Source: https://github.com/fyrsmithlabs/marketplace/tree/main/plugins/fs-dev/skills/agent-artifacts
Command: npx skills add https://github.com/fyrsmithlabs/marketplace --skill agent-artifacts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agent-generated files (plans, tasks, research, reviews, orchestration output) MUST go to docs/.claude/, never the repo root. This directory is gitignored per git-repo-standards.

Core Features & Use Cases

  • Artifact Routing: Direct all agent outputs to docs/.claude/ subdirectories: plans, tasks, research, reviews, orchestration, brainstorms.
  • Automatic Organization: Creates necessary subdirectories as artifacts are produced.
  • Use Case: When an agent produces a brainstorm and a plan, store them under docs/.claude/brainstorms and docs/.claude/plans respectively, avoiding pollution of the repo root.

Quick Start

Use the agent-artifacts policy to ensure any new artifact is saved under docs/.claude/ instead of the repository root.

Frequently Asked Questions about agent-artifacts

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

FAQPage Schema
How do I stop agent-generated files from cluttering my repository root?

To prevent agent artifacts from cluttering the repository root, route all outputs like plans, tasks, and research directly to a dedicated docs/.claude/ directory. This approach enforces project standards by keeping the root clean and organizing files into specific subdirectories automatically.

What is the best way to organize AI agent outputs like brainstorms and plans?

The best way to organize AI agent outputs is to route them into categorized subdirectories within docs/.claude/. Artifacts such as brainstorms, plans, and reviews are automatically sorted into their respective folders, ensuring project standards are maintained without manual filing.

How do I configure artifact routing to use existing repository settings?

Artifact routing honors repository settings by checking the .claude/fs-dev-settings.json file. This configuration ensures that agent outputs are directed to the correct docs/.claude/ subdirectories while strictly avoiding any writes to the repository root.

Does this artifact routing approach work for all types of agent outputs?

Yes, this artifact routing approach works across all agent output types including plans, tasks, research, reviews, orchestration, and brainstorms. It automatically creates the necessary subdirectories within docs/.claude/ as these artifacts are produced.

Why should agent-generated files go into a gitignored directory?

Agent-generated files should go into a gitignored directory like docs/.claude/ to prevent polluting the repository root with temporary or internal outputs. This practice aligns with git-repo-standards, keeping version control history clean and focused on source code.