agent-customization

Enforce architectural routing constraints for enterprise agent customization workflows.

Updated Dec 26, 2025

Search Tags:#automation #workflow #routing #agent #governance #enterprise

Ready to run

npx skills add https://github.com/dthompsonfl/crispy-fishstick --skill agent-customization-dthompsonfl

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-customization
Source: https://github.com/dthompsonfl/crispy-fishstick/tree/main/prompts/skills/agent-customization
Command: npx skills add https://github.com/dthompsonfl/crispy-fishstick --skill agent-customization-dthompsonfl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enterprise teams need a deterministic routing authority to govern agent customization primitives, ensuring architectural integrity and consistent integration across workspaces and ecosystems.

Core Features & Use Cases

Deterministic decision flow via a Strict Architectural Routing Matrix that governs how workspace instructions, file instructions, prompts, hooks, custom agents, and skills are selected and executed.
Clear boundaries between Skill units and Custom Agents, with explicit edge-case handling and mandatory ecosystem integration through AGENTS.md.
Lifecycle-driven creation workflow and prescribed file locations to enable scalable governance across monorepos.

Quick Start

Create a new SKILL.md for the skill under .github/skills/<name>/ with the required frontmatter and body, and register it in AGENTS.md.

Frequently Asked Questions about agent-customization

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

FAQPage Schema

How do I enforce architectural constraints for agent customization in an enterprise workspace?▼

Enterprise agent customization governance requires a deterministic routing authority to enforce architectural constraints across workspaces. This is achieved by applying a strict routing matrix that governs how workspace instructions, file rules, prompts, hooks, and skills are selected and executed.

What is the best way to route deterministic agent workflows across prompts, skills, and hooks?▼

Deterministic agent workflow routing uses a Strict Architectural Routing Matrix to coordinate handoffs across prompts, skills, and hooks. This matrix provides clear boundaries between Skill units and Custom Agents while handling edge cases explicitly.

How do I register a new skill for enterprise agent governance in a monorepo?▼

To register a skill for enterprise agent governance, create a SKILL.md file under .github/skills/<name>/ with required YAML frontmatter and a body documenting the routing matrix, then register the skill in the AGENTS.md file.

Does enterprise agent routing require specific file locations and frontmatter formats?▼

Yes, enterprise agent routing requires YAML frontmatter containing name and description in the SKILL.md file. The file must be placed under .github/skills/<name>/ and prescribe strict routing matrices, edge-case boundaries, and file-specific rules.

When do I need deterministic routing for custom agents versus standard workspace instructions?▼

Deterministic routing for custom agents is needed when enterprise teams require lifecycle-driven creation workflows and coordinated handoffs across project-level agent workflows. It ensures architectural integrity and consistent integration across monorepos.

What are the limitations of using a strict architectural routing matrix for agent customization?▼

A strict architectural routing matrix limits agent customization by enforcing deterministic decision flows and explicit edge-case boundaries. Deviations from prescribed file locations or missing AGENTS.md registration break the governance framework and coordinated handoffs.