Creates .pi/skills from procedural doc sections with proper structure and transformation
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Paths: File paths (
shared/,references/,../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root.
Type: L3 Worker (standalone-capable) Category: 1XX Documentation Pipeline Coordinator: ln-160-docs-skill-extractor (optional)
Creates skill files from procedural documentation sections. Transforms declarative prose into imperative executable instructions.
| Aspect | Details |
|---|---|
| Input | Procedural doc sections (from ln-160 contextStore or standalone scan) |
| Output | .pi/skills/*.md files in target project |
| Template | references/command_template.md |
| Mode | Trigger | Behavior |
|---|---|---|
| Worker | Invoked by ln-160 with contextStore | Use provided sections directly |
| Standalone | Invoked directly with $ARGUMENTS | Self-discover + classify docs |
When invoked directly (not via ln-160):
$ARGUMENTS = file paths -> read those docs, extract procedural sections$ARGUMENTS = "all" or empty -> scan docs/ recursivelyMANDATORY READ: Load ../ln-160-docs-skill-extractor/references/classification_rules.md (standalone mode only)
Receive contextStore with approved procedural sections:
approved_sections:
- source_file: docs/project/runbook.md
section_header: "Deployment"
line_range: [45, 92]
command_name: deploy.md
- source_file: tests/README.md
section_header: "Running Tests"
line_range: [15, 48]
command_name: run-tests.md
MANDATORY READ: Load references/command_template.md
For each approved section:
Read source -- extract section content from source file at specified line range
Detect allowed-tools -- infer from content:
| Content Pattern | Tool |
|---|---|
| bash/sh code blocks, shell commands | Bash |
| File read/load references | Read |
| File modify/update instructions | Edit |
| Search/find in files | Grep, Glob |
| Skill invocations | Skill |
| User confirmation steps | AskUserQuestion |
Transform content using rules below
Write file to .pi/skills/{command_name}
| Rule | From | To |
|---|---|---|
| Voice | Declarative ("The system uses X") | Imperative ("Run X") |
| Code blocks | Preserve as-is | Keep unchanged |
| Numbered lists | Description-style | Ordered workflow steps with ### headers |
| Verification | Implicit ("should work") | Explicit verification commands |
| Doc metadata | SCOPE tags, Maintenance sections | Remove |
| Troubleshooting | Prose | Table format (Issue / Solution) |
| Prerequisites | Mentioned inline | Dedicated Prerequisites table |
| Related docs | Inline references | Related Documentation section with relative links |
Return to coordinator (or display to user in standalone mode):
created:
- file: .pi/skills/deploy.md
source: docs/project/runbook.md#Deployment
lines: 85
tools: [Bash, Read]
- file: .pi/skills/run-tests.md
source: tests/README.md#Running Tests
lines: 62
tools: [Bash]
summary: "Created 2 commands from 2 procedural sections"
references/command_template.md structure.pi/skills/{command_name}Version: 1.0.0 Last Updated: 2026-03-13
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA standards. Use this skill to generate semantic ARIA for Web and accessibility traits for Web and Native platforms (iOS/Android).
中文简介正在准备中。当前显示原文说明。
Whole site or product — a full web accessibility (a11y) audit against WCAG 2.2, following the WCAG-EM methodology. Defines scope, samples representative pages and flows, runs the automated tier (`accessibility-scan`) and the hands-on manual tier (`accessibility-inspect`), and produces one conformance report. Grades each finding by severity and evidence basis, and states per-criterion conformance as pass, fail, or undetermined (needs a human). Use it for 'audit my site for accessibility', 'is this product accessible', 'a11y audit', 'WCAG or Section 508 conformance report', or any multi-page assessment. Assesses; does not fix (use `accessibility-fix`) or diff (use `accessibility-diff`). For a single page use `accessibility-scan`; for hands-on keyboard and screen-reader checks use `accessibility-inspect`.
中文简介正在准备中。当前显示原文说明。
Regression check — diff a live page's web accessibility (a11y) violations against a baseline. By default it compares your uncommitted changes (stash-based); pass `--branch [<name>]` to compare against a branch. Reports the new WCAG violations introduced, the ones fixed, and the count of pre-existing ones. Use it for 'did my change break accessibility', 'what a11y issues did this PR add', or as a CI gate. For a full scan of one page use `accessibility-scan`; for a whole site use `accessibility-audit`.
中文简介正在准备中。当前显示原文说明。
Remediation only — repair web accessibility (a11y) violations against WCAG 2.2 with a baseline, edit, and verify loop. Takes a target (URL, files, directory) or a findings worklist from `accessibility-scan`/`accessibility-inspect`/`accessibility-audit`, applies mechanical fixes as given, leaves TODOs for visual or contextual judgment, and verifies by re-running the baseline check. It only fixes. To find issues use `accessibility-scan` (one page, automated), `accessibility-inspect` (one page, manual), or `accessibility-audit` (whole site, WCAG-EM); to check for regressions use `accessibility-diff`. Use it for 'fix the a11y issues in X', 'make this accessible', 'add missing alt text and labels', 'apply these accessibility fixes', 'remediate these violations'.
中文简介正在准备中。当前显示原文说明。
One page, hands-on manual tier — drive a live page through the web accessibility (a11y) checks a rule engine can't decide: keyboard operation and focus order, screen-reader names, roles and states from the accessibility tree, reflow and zoom, reduced motion, form errors, and target size. Grades each finding by evidence basis (verified / confirm-with-a-human / human-required) and severity, and closes every criterion in a ledger: verified, flagged, not exercised, or N/A. Locates and assesses; does not fix (use `accessibility-fix`). Use it for keyboard testing, focus-order checks, screen-reader or a11y-tree review, reflow and zoom at 200%, or 'is this operable, not just lint-clean'. The automated tier is `accessibility-scan`; `accessibility-audit` runs both across a sampled site.
中文简介正在准备中。当前显示原文说明。
One page, automated tier — run the web accessibility (a11y) rule engine against a live page and locate every violation it can detect mechanically. Pass a URL, a config target name (e.g. `accesslint:accessibility-scan dev`), or nothing to use the default target from `accesslint.config.json`. Ensures a debuggable Chrome, runs the @accesslint/core engine over CDP, and returns a worklist of live-DOM WCAG 2.2 violations, each grounded to its DOM selector and source `file:line`. Locates; doesn't edit. Use it for 'is this page accessible', 'check a11y on this URL', 'find contrast and alt-text issues', or to verify a UI change. For hands-on keyboard and screen-reader checks use `accessibility-inspect`; for a whole site or product use `accessibility-audit`; to diff against uncommitted changes or a branch use `accessibility-diff`.
中文简介正在准备中。当前显示原文说明。