How do I install the Library Weapon skill?

Run npx skillmds@latest add the-notorious-avengers/library-weapon 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 Library Weapon 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 Library Weapon?

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 Library Weapon free to use?

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

Who published Library Weapon?

The-Notorious-Avengers (@the-notorious-avengers) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Library Weapon by the-notorious-avengers

Name: Library Weapon
Rating: 4.2 (5 reviews)
Author: The-Notorious-Avengers

Library Weapon

Equips library-guardian with the documentation lifecycle — knowledge-base authoring (public vs private audience split), feature PRD authoring (prd-<###>-<slug>/ with index + sub-PRDs + qa/), issue IRD authoring (ird-<###>-<slug>/ with index + qa/), backwards-PRD generation, sync audits / drift detection, lifecycle moves (backlog/in-work/completed), and the standardize-library script for scaffolding any repo to schema v2. Use when initializing a library/, ingesting issues, planning features, writing knowledge docs, running drift audits, or moving a completed PRD/IRD to its completed/ tier. Not for QA report authorship (use quality-weapon) or asset-registry work (use asset-weapon).

File contents

library-weapon

Cursor-skill wrapper for the library-guardian Angel's companion resource bundle. The full directory map, intent-routing tables, examples catalog, templates list, path conventions, and self-operation notes are in README.md — start there.

Agent entry point: library-guardian.md — deployed via the host repo's .cursor/agents/ folder.

Peer Angels: quality-guardian owns QA report authorship. asset-guardian owns the parallel asset registry.

Path conventions enforced (schema v2)

Output	Location
Customer-facing docs	`library/knowledge/public/<domain>/<slug>.md`
Internal engineering/business docs	`library/knowledge/private/<domain>/<slug>.md`
ADRs	`library/knowledge/private/architecture/ADR-<n>-<slug>.md`
PRD folder (backlog)	`library/requirements/backlog/prd-<###>-<slug>/`
PRD index	`library/requirements/backlog/prd-<###>-<slug>/prd-<###>-<slug>-index.md`
PRD sub-feature	`library/requirements/backlog/prd-<###>-<slug>/prd-<###><letter>-<slug>-<feature>.md`
PRD QA report	`library/requirements/backlog/prd-<###>-<slug>/qa/prd-<###>-<slug>-qa.md`
PRD in-work	`library/requirements/in-work/prd-<###>-<slug>/` (same structure)
Completed PRD	`library/requirements/completed/prd-<###>-<slug>/`
Routine scan report	`library/requirements/reports/<YYYY-MM-DD>-<type>-report.md`
IRD folder (backlog)	`library/issues/backlog/ird-<###>-<slug>/`
IRD index	`library/issues/backlog/ird-<###>-<slug>/ird-<###>-<slug>-index.md`
IRD QA report	`library/issues/backlog/ird-<###>-<slug>/qa/ird-<###>-<slug>-qa.md`
Completed IRD	`library/issues/completed/ird-<###>-<slug>/`
Notes (human only)	`library/notes/` — agents NEVER write here

NOT in library/:

Asset	Correct location
Brand assets (logos, fonts, colors)	Wherever the deployment stores shared brand assets (e.g. a `brands/` or `assets/` folder outside this repo)
Derived wiki / docs vault mirrors	Any aggregated wiki or docs vault that mirrors `library/` is derived — never edit it directly
Binary files (images, fonts, PDFs)	An `assets/` or `public/` folder appropriate to the deployment

Legacy v1 paths (do NOT create new content here):

v1 path	v2 replacement
`library/knowledge-base/`	`library/knowledge/private/`
`library/architecture/`	`library/knowledge/private/architecture/`
`library/requirements/features/`	`library/requirements/backlog/`
`library/requirements/issues/`	`library/issues/backlog/`
`library/qa/`	`library/requirements/reports/`

See guides/07-wiki-sync.md for the wiki-sync contract.

---name: library-weapondescription: Equips library-guardian with the documentation lifecycle — knowledge-base authoring (public vs private audience split), feature PRD authoring (prd-<###>-<slug>/ with index + sub-PRDs + qa/), issue IRD authoring (ird-<###>-<slug>/ with index + qa/), backwards-PRD generation, sync audits / drift detection, lifecycle moves (backlog/in-work/completed), and the standardize-library script for scaffolding any repo to schema v2. Use when initializing a library/, ingesting issues, planning features, writing knowledge docs, running drift audits, or moving a completed PRD/IRD to its completed/ tier. Not for QA report authorship (use quality-weapon) or asset-registry work (use asset-weapon).---# library-weaponCursor-skill wrapper for the `library-guardian` Angel's companion resource bundle. The full directory map, intent-routing tables, examples catalog, templates list, path conventions, and self-operation notes are in [`README.md`](README.md) — start there.> **Agent entry point:** [`library-guardian.md`](../../agents/library-guardian.md) — deployed via the host repo's `.cursor/agents/` folder.>> **Peer Angels:** [`quality-guardian`](../../agents/quality-guardian.md) owns QA report authorship. [`asset-guardian`](../../agents/asset-guardian.md) owns the parallel asset registry.## Path conventions enforced (schema v2)| Output | Location ||---|---|| Customer-facing docs | `library/knowledge/public/<domain>/<slug>.md` || Internal engineering/business docs | `library/knowledge/private/<domain>/<slug>.md` || ADRs | `library/knowledge/private/architecture/ADR-<n>-<slug>.md` || PRD folder (backlog) | `library/requirements/backlog/prd-<###>-<slug>/` || PRD index | `library/requirements/backlog/prd-<###>-<slug>/prd-<###>-<slug>-index.md` || PRD sub-feature | `library/requirements/backlog/prd-<###>-<slug>/prd-<###><letter>-<slug>-<feature>.md` || PRD QA report | `library/requirements/backlog/prd-<###>-<slug>/qa/prd-<###>-<slug>-qa.md` || PRD in-work | `library/requirements/in-work/prd-<###>-<slug>/` (same structure) || Completed PRD | `library/requirements/completed/prd-<###>-<slug>/` || Routine scan report | `library/requirements/reports/<YYYY-MM-DD>-<type>-report.md` || IRD folder (backlog) | `library/issues/backlog/ird-<###>-<slug>/` || IRD index | `library/issues/backlog/ird-<###>-<slug>/ird-<###>-<slug>-index.md` || IRD QA report | `library/issues/backlog/ird-<###>-<slug>/qa/ird-<###>-<slug>-qa.md` || Completed IRD | `library/issues/completed/ird-<###>-<slug>/` || Notes (human only) | `library/notes/` — agents NEVER write here |**NOT in `library/`:**| Asset | Correct location ||---|---|| Brand assets (logos, fonts, colors) | Wherever the deployment stores shared brand assets (e.g. a `brands/` or `assets/` folder outside this repo) || Derived wiki / docs vault mirrors | Any aggregated wiki or docs vault that mirrors `library/` is derived — never edit it directly || Binary files (images, fonts, PDFs) | An `assets/` or `public/` folder appropriate to the deployment |**Legacy v1 paths (do NOT create new content here):**| v1 path | v2 replacement ||---|---|| `library/knowledge-base/` | `library/knowledge/private/` || `library/architecture/` | `library/knowledge/private/architecture/` || `library/requirements/features/` | `library/requirements/backlog/` || `library/requirements/issues/` | `library/issues/backlog/` || `library/qa/` | `library/requirements/reports/` |See `guides/07-wiki-sync.md` for the wiki-sync contract.

Frequently asked questions