profile-design

Design and validate BotMinter profile templates with role and process definitions.

18|4|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/botminter/botminter --skill profile-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: profile-design
Source: https://github.com/botminter/botminter/tree/main/minty/.claude/skills/profile-design
Command: npx skills add https://github.com/botminter/botminter --skill profile-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, repeatable way to design, fork, and repair BotMinter profile templates so teams have consistent roles, hats, skills, statuses, and process conventions before they are instantiated as live team repos. It removes the guesswork of missing skeleton files, mismatched status lifecycles, incomplete hat triggers, and broken profile manifests so profiles validate and behave predictably when applied.

Core Features & Use Cases

  • Guided role design that generates the required coding-agent skeleton files and hat instruction pages.
  • Process and status lifecycle design with manifest updates and PROCESS.md generation to ensure roles map to status handlers.
  • Forking and customization of existing profiles while preserving agreements, knowledge, and validation checks.
  • Troubleshooting and validation: manifest parsing, status coverage checks, hat trigger validation, board-scanner dispatch completeness, and skeleton file presence.
  • Use case: Create a new feature-development profile, add a chief-of-staff role with review gates, and run the validation checklist to ensure no statuses are orphaned.

Quick Start

Request a profile design by asking the assistant to create a new profile named acme with roles product-owner and developer and a three-stage status lifecycle.

Frequently Asked Questions about profile-design

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

FAQPage Schema
How do I design a BotMinter profile template with custom roles and status lifecycles?

To design a BotMinter profile template, you define custom roles and status lifecycles, which generates the required coding-agent skeleton files, hat instruction pages, and PROCESS.md updates to ensure roles map correctly to status handlers.

Why does my BotMinter profile validation fail with orphaned statuses and broken hat triggers?

BotMinter profile validation fails when hat triggers are incomplete, statuses are orphaned without handlers, or required skeleton files are missing. Troubleshooting checks manifest parsing, status coverage, and board-scanner dispatch completeness to locate and repair these mismatches.

What is the best way to fork an existing BotMinter profile without losing agreements and knowledge paths?

Forking an existing BotMinter profile preserves original agreements, knowledge paths, and validation checks while allowing customization. This structured duplication ensures the new profile template validates correctly and maintains consistent process conventions before instantiation.

Can I use profile-design to add a chief-of-staff role with review gates to an existing feature-development profile?

Yes, you can add a chief-of-staff role with review gates to a feature-development profile. The guided role design updates the profile manifest, generates necessary hat instruction pages, and runs a validation checklist to ensure no statuses are orphaned.

What files need to be consistent when troubleshooting a BotMinter profile manifest?

Troubleshooting a BotMinter profile manifest requires consistency between botminter.yml and PROCESS.md. Validation also checks for required coding-agent skeleton files, ralph.yml skill_dirs, hat trigger validity, and existing agreements and knowledge paths.

Does profile-design require any dependencies or external components to validate profile templates?

No, profile-design operates with zero external dependencies or components. It runs self-contained validation checks for manifest parsing, hat trigger validity, board-scanner dispatch completeness, and skeleton file presence directly during profile development or repair.