refer

Owns a nested reference fixture for testing nested-reference and reference-toc lint checks.

3|1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/AlmogBaku/aos --skill refer-almogbaku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: refer
Source: https://github.com/AlmogBaku/aos/tree/main/tools/lint/selftest/fixture/capabilities/name-cap/skills/refer
Command: npx skills add https://github.com/AlmogBaku/aos --skill refer-almogbaku

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? This Skill provides a controlled test fixture that exercises lint rules for nested references and reference table-of-contents validation, letting tooling authors verify that linters correctly detect violations in skill reference files. ## Core Features & Use Cases - Nested Reference Fixture: Contains a reference/long.md file that links to reference/deep.md, deliberately triggering nested-reference violations. - Reference TOC Violation: Ships a long reference file with no Contents block and past the line limit to test reference-toc checks. - Dangling Link Cases: Includes dangling {{skill: kapture}} and {{agent: ghost}} references plus escaped variants that must not fire, validating linter precision. - Use Case: A developer maintaining the aos lint tooling runs the selftest suite, and this fixture confirms the linter flags nested references, missing TOCs, and dangling cross-skill links while ignoring escaped placeholders. ## Quick Start Run the lint selftest suite against this fixture to verify nested-reference and reference-toc violations are detected correctly.

Frequently Asked Questions about refer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is this refer skill used for?▼

It is a lint selftest fixture that owns a nested reference, used to verify that lint checks for nested-reference and reference-toc violations fire correctly. It is not an end-user capability but part of the tooling test suite.

How do I test nested reference lint rules?▼

Run the lint selftest suite that includes this fixture. The reference/long.md file links to deep.md, creating a nested-reference violation the linter must detect, while backtick-style mentions test alternate detection paths.

Why does long.md have no Contents block?▼

The missing Contents block is intentional. The file exceeds the line limit without a table of contents, which deliberately triggers the reference-toc lint rule so the selftest can confirm the rule fires.

What are the dangling skill and agent references?▼

The SKILL.md contains {{skill: kapture}} and {{agent: ghost}} placeholders pointing to nonexistent targets, testing dangling-link detection. Escaped variants with backslashes must not fire, validating linter precision.

Can I use this fixture as a template for real skills?▼

No. This fixture is deliberately full of lint violations for testing purposes. Copying it would introduce nested references, missing TOCs, and dangling links into your own skills.