How do I install the Aidd Docio skill?

Run npx skillmds add majiayu000/aidd-docio 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 Aidd Docio safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Aidd Docio?

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 Aidd Docio free to use?

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

Who published Aidd Docio?

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

Aidd Docio by majiayu000 — Agent Skill

Name: Aidd Docio
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Scope

This skill owns shared DocIO runtime entrypoints.
Stage skills consume these APIs for preflight/postflight and deterministic document updates.
Flow-state orchestration remains in feature-dev-aidd:aidd-core and feature-dev-aidd:aidd-loop.

Canonical shared Python entrypoints

python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-docio/runtime/md_slice.py
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-docio/runtime/md_patch.py
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-docio/runtime/actions_validate.py
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-docio/runtime/actions_apply.py
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-docio/runtime/context_map_validate.py
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-docio/runtime/context_expand.py

Command contracts

`python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-docio/runtime/md_slice.py`

When to run: when stage or subagent needs bounded section reads instead of full-file scans.
Inputs: source markdown path with heading/line selectors.
Outputs: deterministic excerpt payload for pack-first evidence workflows.
Failure mode: non-zero exit on missing file, invalid selectors, or malformed markdown boundaries.
Next action: fix selectors/source path and rerun the same slice command.

`python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-docio/runtime/actions_apply.py`

When to run: stage-chain postflight after validated *.actions.json is available.
Inputs: --actions <path> with optional apply-log paths and stage context.
Outputs: applied updates, progress synchronization, and downstream stage artifacts.
Failure mode: non-zero exit on schema violations, write failures, or boundary guard blocks.
Next action: inspect apply log, fix action payload/root cause, then rerun stage-chain postflight.

Ownership guard

DocIO-facing runtime modules must be implemented under skills/aidd-docio/runtime/*.
Consumers should reference skills/aidd-docio/runtime/* as canonical paths.

Additional resources

references/read-write-maps.md (when: readmap/writemap behavior is in question; why: align map validation and expansion semantics).
references/actions-flow.md (when: actions schema/apply behavior is unclear; why: follow validator-to-apply lifecycle).

---name: aidd-dociodescription: Owns shared DocIO runtime for markdown slicing/patching, actions validation/apply, and context-map expansion. Use when stage skills need canonical DocIO operations.--- ## Scope - This skill owns shared DocIO runtime entrypoints. - Stage skills consume these APIs for preflight/postflight and deterministic document updates. - Flow-state orchestration remains in `feature-dev-aidd:aidd-core` and `feature-dev-aidd:aidd-loop`. ## Canonical shared Python entrypoints - `python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-docio/runtime/md_slice.py` - `python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-docio/runtime/md_patch.py` - `python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-docio/runtime/actions_validate.py` - `python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-docio/runtime/actions_apply.py` - `python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-docio/runtime/context_map_validate.py` - `python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-docio/runtime/context_expand.py` ## Command contracts ### `python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-docio/runtime/md_slice.py` - When to run: when stage or subagent needs bounded section reads instead of full-file scans. - Inputs: source markdown path with heading/line selectors. - Outputs: deterministic excerpt payload for pack-first evidence workflows. - Failure mode: non-zero exit on missing file, invalid selectors, or malformed markdown boundaries. - Next action: fix selectors/source path and rerun the same slice command. ### `python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-docio/runtime/actions_apply.py` - When to run: stage-chain postflight after validated `*.actions.json` is available. - Inputs: `--actions <path>` with optional apply-log paths and stage context. - Outputs: applied updates, progress synchronization, and downstream stage artifacts. - Failure mode: non-zero exit on schema violations, write failures, or boundary guard blocks. - Next action: inspect apply log, fix action payload/root cause, then rerun stage-chain postflight. ## Ownership guard - DocIO-facing runtime modules must be implemented under `skills/aidd-docio/runtime/*`. - Consumers should reference `skills/aidd-docio/runtime/*` as canonical paths. ## Additional resources - [references/read-write-maps.md](references/read-write-maps.md) (when: readmap/writemap behavior is in question; why: align map validation and expansion semantics). - [references/actions-flow.md](references/actions-flow.md) (when: actions schema/apply behavior is unclear; why: follow validator-to-apply lifecycle).

Frequently asked questions