Plugin Help
Apps & Automationplugin-helpPlugin Help is an Agent Skill for apps & automation published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Show available commands and explain how to use the Gotrino inclusion plugin.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/plugin-help/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/plugin-help, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Plugin Help
Show available commands and explain how to use the Gotrino inclusion plugin.
Output
# Gotrino - Inclusion Plugin
Tools to help you write more inclusive code.
## Quick Reference
### Fast Checks (run anytime)
| Command | What it does |
|---------|--------------|
| `/guardian [path]` | Quick inclusion gut-check (lightweight) |
| `/language-check [path]` | Scan for non-inclusive language |
| `/names-check [path]` | Check name diversity in examples |
| `/i18n-check [path]` | Find internationalization issues |
### Deeper Analysis
| Command | What it does |
|---------|--------------|
| `/examples-audit [path]` | Analyze mock data for cultural assumptions |
| `/inclusion-audit [path]` | Comprehensive inclusion review |
| `/test-assumption [path]` | Identify hidden assumptions about users |
### Utilities
| Command | What it does |
|---------|--------------|
| `/inclusive-names` | Generate diverse name suggestions |
| `/explain [path]` | Create decision record in `decisions/` |
| `/impact [path]` | Analyze change impact before making it |
### Setup
| Command | What it does |
|---------|--------------|
| `/teach-charter` | Configure plugin for your project |
## Typical Workflow
**Starting a new project:**
1. Run `/teach-charter` to set up your `.inclusion-config.md`
2. Define your scope (US-only? Global? etc.)
3. Set priorities for your team
**During development:**
- Run `/guardian` after generating forms, UI, or examples
- Chain it: "create the signup form, then /guardian it"
- Run focused checks (`/language-check`, `/names-check`) as needed
**Before shipping:**
- Run `/inclusion-audit` for comprehensive review
- Run `/test-assumption` on user-facing flows
## Configuration
Your settings are stored in `.inclusion-config.md`:
- **Scope decisions**: What's in/out of scope (e.g., i18n for US-only products)
- **Acknowledged findings**: Issues you've reviewed and accepted
- **Priorities**: What matters most for your project
- **Decisions location**: Where `/explain` saves decision records (default: `decisions/`)
Run `/teach-charter` to create or update this file.
## Philosophy
This plugin isn't a linter. It's a **second pair of eyes** that asks:
> "Who might this exclude? What assumptions are baked in?"
It won't catch everything, and not everything it catches needs fixing. Use judgment. The goal is code that welcomes more users, not compliance with rules.
Process
- Output the help text above
- If
.inclusion-config.mdexists, note: "Config loaded. Run/teach-charterto view or update." - If no config exists, note: "No config found. Run
/teach-charterto set up your project."