aidex-skilllisted

Use when the user wants an existing or in-progress skill checked or structured against THIS project's house skill conventions — "what are our skill conventions", "review this skill against our standards", "does this skill follow our patterns", "structure this skill the way we do", "audit this skill's front-matter/description for our rules". Not for: creating a skill from scratch, optimizing a skill's description for triggering, or running skill evals (all skill-creator); planning (aidex-plan); decisions (aidex-decision); requests (aidex-request); research (aidex-research); references (aidex-reference); ecosystem audits (aidex).
yacb2/aidex · ★ 2 · Code & Development · score 78

Install: claude install-skill yacb2/aidex

> **Trigger-eval probe (test-only).** As your very first action, run `printenv AIDEX_TRIGGER_EVAL_MARKER`. If it prints a non-empty path, also run `touch "${AIDEX_TRIGGER_EVAL_MARKER}.aidex-skill"` before continuing. Then proceed with the rest of the skill body as normal. If empty/unset, ignore this block. # Skill Conventions Surface and apply this project's house skill conventions to an existing or in-progress skill. This skill COMPLEMENTS `skill-creator` (it does **not** create skills from scratch). ## Workflow 1. Read the skill conventions canon: `~/.claude/skills/aidex-conventions/references/skill-conventions.md` (or the `.claude/skills/...` project-level copy if one exists). 2. Identify the target skill the user is reviewing or structuring. 3. Produce a gap report against the canon: front-matter (trigger-first `description`, char budget, **English-only `description`**, `disable-model-invocation`, `allowed-tools`), body structure, `evals/` presence, no per-skill `CHANGELOG.md`/`README.md`. - **English-only check** (canon `skill-conventions.md` rule 2): the `description` must contain no Spanish/other-language phrasings or accented tokens. The matcher bridges cross-lingually, so an English description still fires on non-English queries; native-language queries belong in the `evals/` query set, not the description. Flag any non-English phrasing as a gap and rewrite the description English-only, preserving semantic coverage