How do I install the Aidex Skill skill?

Run npx skillmds@latest add yacb2/aidex-skill 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 Aidex Skill 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 Aidex Skill?

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 Aidex Skill free to use?

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

Who published Aidex Skill?

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

Aidex Skill by yacb2 — Agent Skill

Name: Aidex Skill
Author: yacb2

Aidex Skill

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 d9acc86 3 files · 8.7 KB Updated Sep 17, 2026

File contents

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

Read the skill conventions canon: ~/.claude/skills/aidex-conventions/references/skill-conventions.md (or the .claude/skills/... project-level copy if one exists).
Identify the target skill the user is reviewing or structuring.
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 (drop the foreign phrasings; keep their English equivalents).
Writes go only to the target skill's own files (SKILL.md, evals/) — never to the canon under references/, which this skill reads read-only.

Boundaries

The user wants to…	Route to
Create a skill from scratch / optimize a description / run skill evals	`skill-creator`
Plan multi-step / multi-phase implementation work	`aidex-plan`
Record a decision / ADR	`aidex-decision`
Capture a stakeholder/client request	`aidex-request`
Investigate / research how something works	`aidex-research`
Document a settled system reference	`aidex-reference`
Audit the Claude Code ecosystem	`aidex`

skill-creator — owns skill creation, description optimization, and eval running; this skill only checks/applies house conventions.
aidex-conventions — owns the shared documentation canon (this skill reads its references/skill-conventions.md).

---name: aidex-skilldescription: 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).---> **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 ConventionsSurface and apply this project's house skill conventions to an existing orin-progress skill. This skill COMPLEMENTS `skill-creator` (it does **not**create skills from scratch).## Workflow1. 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 (drop the foreign phrasings; keep their English equivalents).4. Writes go only to the target skill's own files (`SKILL.md`, `evals/`) — never to the canon under `references/`, which this skill reads read-only.## Boundaries| The user wants to… | Route to ||---|---|| Create a skill from scratch / optimize a description / run skill evals | `skill-creator` || Plan multi-step / multi-phase implementation work | `aidex-plan` || Record a decision / ADR | `aidex-decision` || Capture a stakeholder/client request | `aidex-request` || Investigate / research how something works | `aidex-research` || Document a settled system reference | `aidex-reference` || Audit the Claude Code ecosystem | `aidex` |## Related- **skill-creator** — owns skill creation, description optimization, and eval running; this skill only checks/applies house conventions.- **aidex-conventions** — owns the shared documentation canon (this skill reads its `references/skill-conventions.md`).

Frequently asked questions