How do I install the Configuration skill?

Run npx skillmds@latest add austin1howard/configuration in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Configuration safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Configuration?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Configuration free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Configuration?

austin1howard (@austin1howard) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Configuration by austin1howard — Agent Skill

Name: Configuration
Author: austin1howard

File contents

alphabetsoup:configuration

1 — Register the marketplace

Add to your project's .claude/settings.json:

{
  "extraKnownMarketplaces": [
    { "github": "austin1howard/alphabetsoup" }
  ]
}

Then install the core plugin:

/plugin install alphabetsoup@alphabetsoup

2 — Detect your stack and enable plugins

Signal	Plugin
`go.mod` present	`gale@alphabetsoup` (Go backend)
`*.py` or `pyproject.toml` present	`pat@alphabetsoup` (Python backend)
`package.json` with `"vue"` dep	`vic@alphabetsoup` (Vue 3 frontend)
`package.json` with `"react"` dep	`randy@alphabetsoup` (React frontend)

Also enable aspen@alphabetsoup (architect) for any project that uses specs/.

Install detected plugins:

/plugin install aspen@alphabetsoup
/plugin install <detected>@alphabetsoup

Enable them in .claude/settings.json:

{
  "enabledPlugins": ["aspen@alphabetsoup", "gale@alphabetsoup"]
}

3 — Declare active agents in CLAUDE.md

Add an ## alphabetsoup agents section to the project's CLAUDE.md. List only the roles in use:

## alphabetsoup agents

- Architect: `aspen`
- Backend: `<plugin-name>`   <!-- e.g. gale, pat -->
- Frontend: `<plugin-name>`  <!-- e.g. vic, randy -->

Omit roles not applicable to this project (e.g. no Frontend line for a backend-only repo). The coordination skill reads this section to resolve which agent to dispatch for each role.

4 — Scaffold project directories

Create standard directories if missing:

specs/          # source of truth — aspen owns this
backend/        # backend engineer agent
frontend/       # frontend engineer agent

5 — Skill namespacing

Skills from this marketplace are invoked as <plugin>:<skill>. Examples:

/alphabetsoup:configuration — this skill
/alphabetsoup:coordination — orchestration loop
Agents are invoked as subagents by plugin name: aspen (architect), or the name of the installed engineer plugin

---name: configurationdescription: Configure the alphabetsoup marketplace in your project: register the marketplace, detect your stack, enable the right plugins, and scaffold standard directories.---# alphabetsoup:configuration## 1 — Register the marketplaceAdd to your project's `.claude/settings.json`:```json{ "extraKnownMarketplaces": [ { "github": "austin1howard/alphabetsoup" } ]}```Then install the core plugin:```/plugin install alphabetsoup@alphabetsoup```## 2 — Detect your stack and enable plugins| Signal | Plugin ||--------|--------|| `go.mod` present | `gale@alphabetsoup` (Go backend) || `*.py` or `pyproject.toml` present | `pat@alphabetsoup` (Python backend) || `package.json` with `"vue"` dep | `vic@alphabetsoup` (Vue 3 frontend) || `package.json` with `"react"` dep | `randy@alphabetsoup` (React frontend) |Also enable `aspen@alphabetsoup` (architect) for any project that uses `specs/`.Install detected plugins:```/plugin install aspen@alphabetsoup/plugin install <detected>@alphabetsoup```Enable them in `.claude/settings.json`:```json{ "enabledPlugins": ["aspen@alphabetsoup", "gale@alphabetsoup"]}```## 3 — Declare active agents in CLAUDE.mdAdd an `## alphabetsoup agents` section to the project's `CLAUDE.md`. List only the roles in use:```markdown## alphabetsoup agents- Architect: `aspen`- Backend: `<plugin-name>` - Frontend: `<plugin-name>` ```Omit roles not applicable to this project (e.g. no `Frontend` line for a backend-only repo). The coordination skill reads this section to resolve which agent to dispatch for each role.## 4 — Scaffold project directoriesCreate standard directories if missing:```specs/ # source of truth — aspen owns thisbackend/ # backend engineer agentfrontend/ # frontend engineer agent```## 5 — Skill namespacingSkills from this marketplace are invoked as `<plugin>:<skill>`. Examples:- `/alphabetsoup:configuration` — this skill- `/alphabetsoup:coordination` — orchestration loop- Agents are invoked as subagents by plugin name: `aspen` (architect), or the name of the installed engineer plugin

Frequently asked questions

Configuration