prodagent:setup

Discover user commands and write a prodagent TOML config file.

1|1|Updated May 9, 2026
One-click install
npx skills add https://github.com/butterflyskies/claude-marketplace --skill prodagent-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prodagent:setup
Source: https://github.com/butterflyskies/claude-marketplace/tree/main/plugins/prodagent/skills/setup
Command: npx skills add https://github.com/butterflyskies/claude-marketplace --skill prodagent-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the setup of a prodagent configuration tailored to the user's workflow, discovering commonly used commands, proposing policy decisions, and writing the final config.

Core Features & Use Cases

  • Custom Config Setup: Guides the user through creating a .config/prodagent/config.toml that reflects their workflow.
  • Command Discovery: Discovers commonly used commands through opt-in scan of shell history and Claude Code session logs.
  • Policy Proposals: Proposes policy decisions with explanations and allows interactive refinement.
  • Final Config Generation: Writes the final config file that can be used by prodagent's command policy engine.

Quick Start

Use the prodagent:setup skill to create a custom prodagent configuration.

Frequently Asked Questions about prodagent:setup

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

FAQPage Schema
How do I configure a prodagent policy engine for my AI coding agent?

To configure a prodagent policy engine, the prodagent:setup skill discovers your commonly used commands, proposes command policy decisions, and writes a final TOML config file tailored to your workflow.

What is the best way to generate a prodagent config file from existing shell history?

The best way to generate a prodagent config file from shell history is using an automated setup process that scans your shell history and Claude Code session logs to propose accurate command policies.

Can I interactively refine proposed command policies before writing the final config?

You can interactively refine proposed command policies during the configuration process, allowing you to review explanations and adjust policy decisions before the final TOML file is written.

Does prodagent configuration require manual TOML file writing for custom workflows?

Prodagent configuration does not require manual TOML writing because the setup skill guides you through custom workflow creation and automatically writes the final config file to your config directory.

What commands are discovered when setting up an AI coding agent command policy?

When setting up a command policy, the discovery process scans opt-in shell history and Claude Code session logs to identify your commonly used commands for accurate policy proposals.

Where does the prodagent setup process write the final configuration file?

The prodagent setup process writes the final configuration file to the `.config/prodagent/config.toml` path, ensuring it is immediately usable by the command policy engine.