AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Aidex Reference

skill-yacb2-aidex-aidex-reference · by yacb2

Use when the user wants to document how an existing, settled part of the system works as an evergreen `.context/references/` module — architecture, configuration, an operational runbook, a how-it-works guide. Fires on "create a reference for X", "document how X works", "write up the X architecture", "document the X configuration", "write a runbook for X". Not for: planning multi-step work (aidex-…

↗ Website ↗ Repository
— No reviews yet
0 installs
10 views
0.0% view→install

Install

$ agentstack add skill-yacb2-aidex-aidex-reference

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-yacb2-aidex-aidex-reference)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 29d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Aidex Reference? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

> 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-reference" before continuing. Then proceed with the rest of the skill body as normal. If empty/unset, ignore this block.

Reference

Document how a settled part of the system works as an evergreen module in .context/references//. This skill is the single-purpose entry point for reference documentation; the formatting canon lives in the shared aidex-conventions reference package (not forked here).

Workflow

  1. Read the reference conventions canon:

~/.claude/skills/aidex-conventions/references/reference-conventions.md (or .claude/skills/aidex-conventions/references/reference-conventions.md if a project-level copy exists).

  1. Create a topic module: .context/references// with 00-index.md

plus sequential NN-.md files. Reference filenames carry no date — references are evergreen, updated in place, no _archive/.

  1. Front-matter per the canon: title, status, created, updated,

version (semantic X.Y.Z). References are exempt from the status-vocabulary check.

  1. Body per the canon module template: Overview, Prerequisites,

main sections with language-hinted code blocks, Verification, Version history. Write the artifact in English (canon §Language).

Self-check (mandatory close step)

Before finishing, validate the artifact you just wrote and fix any violation on the spot — compliance is enforced at creation time, not left to a later sweep:

python3 ~/.claude/skills/aidex-conventions/scripts/validate.py --type references

If the project carries a ratchet baseline (.context/.validate-baseline.json), a non-zero exit means you introduced a NEW violation — fix it before closing.

Boundaries

| The user wants to… | Route to | |---|---| | Plan multi-step / multi-phase implementation work | aidex-plan | | Record a decision / ADR | aidex-decision | | Capture a stakeholder/client request | aidex-request | | Investigate / explore something not yet settled | aidex-research | | Defer / park / shelve an idea for later | aidex-backlog | | Audit the Claude Code ecosystem | aidex | | Audit project state (UX/security/perf/a11y) | aidex-audit |

Related

  • aidex-conventions — owns the shared documentation canon (this skill

delegates into its references/reference-conventions.md).

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

  • Author: yacb2
  • Source: yacb2/aidex
  • License: MIT
  • Homepage: https://aidex-lemon.vercel.app

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills