How do I install the Pkc Link skill?

Run npx skillmds@latest add spillwavesolutions/pkc-link 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 Pkc Link safe to use?

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

Which AI agents work with Pkc Link?

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 Pkc Link free to use?

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

Who published Pkc Link?

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

Pkc Link by spillwavesolutions — Agent Skill

Name: Pkc Link
Author: spillwavesolutions

Pkc Link

Add a typed edge between two OKF concepts (satisfies, implements, designed_by, decides, informs, originates_from, tracks, maps_to, etc.). Use when connecting meetings to decisions, features to requirements, or tickets to work concepts.

File contents

PKC Link

Add reviewable, typed relations so impact analysis and progressive disclosure work across formal and informal knowledge.

Recommended relations (PKC + OKF)

rel	Typical direction	Meaning
`satisfies`	Feature → Requirement	Feature meets requirement
`implements`	CodeChange/Ticket → Feature/Design	Implementation
`designed_by`	Feature → Design	Design shapes feature
`decides`	DecisionRecord → Feature/Design/Requirement	Decision governs target
`informs`	Experiment/Discovery → Feature/Design/Requirement	Evidence influences
`discovered_in`	Finding → Discovery	Nested finding
`originates_from`	DecisionRecord → Meeting/Experiment	Provenance
`lands_in` / `released_in`	CodeChange/Feature → Release	Shipping
`tracks`	TicketLink → work concept	Work tracking
`maps_to`	TicketLink → external	External id map
`depends_on`	any → any	Hard dependency
`related_to`	any → any	Soft link
`supersedes`	newer → older	Replacement
`verified_by`	Test → Feature	Verification

Process

Confirm both concept paths (absolute in-bundle preferred: /features/….md).

Add edge:

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/pkc_link.py" \
  decisions/use-jwt-for-session.md \
  /features/user-authentication.md \
  --rel decides \
  --repo .

Always keep a human-readable Markdown body link in addition to links[].rel.
Never invent edges — only record real relationships the user affirmed or that are evident in the source material.
Unknown rel values are allowed (OKF flags as info).

Done when

Frontmatter links entry exists on the source
Body contains a Markdown link to the target
Log updated when a new edge is created

---name: pkc-linkdescription: Add a typed edge between two OKF concepts (satisfies, implements, designed_by, decides, informs, originates_from, tracks, maps_to, etc.). Use when connecting meetings to decisions, features to requirements, or tickets to work concepts.---# PKC LinkAdd reviewable, typed relations so impact analysis and progressive disclosure work across formal and informal knowledge.## Recommended relations (PKC + OKF)| rel | Typical direction | Meaning ||-----|-------------------|---------|| `satisfies` | Feature → Requirement | Feature meets requirement || `implements` | CodeChange/Ticket → Feature/Design | Implementation || `designed_by` | Feature → Design | Design shapes feature || `decides` | DecisionRecord → Feature/Design/Requirement | Decision governs target || `informs` | Experiment/Discovery → Feature/Design/Requirement | Evidence influences || `discovered_in` | Finding → Discovery | Nested finding || `originates_from` | DecisionRecord → Meeting/Experiment | Provenance || `lands_in` / `released_in` | CodeChange/Feature → Release | Shipping || `tracks` | TicketLink → work concept | Work tracking || `maps_to` | TicketLink → external | External id map || `depends_on` | any → any | Hard dependency || `related_to` | any → any | Soft link || `supersedes` | newer → older | Replacement || `verified_by` | Test → Feature | Verification |## Process1. Confirm both concept paths (absolute in-bundle preferred: `/features/….md`).2. Add edge: ```bash python3 "${CLAUDE_PLUGIN_ROOT}/scripts/pkc_link.py" \ decisions/use-jwt-for-session.md \ /features/user-authentication.md \ --rel decides \ --repo . ```3. Always keep a human-readable Markdown body link in addition to `links[].rel`.4. Never invent edges — only record real relationships the user affirmed or that are evident in the source material.5. Unknown `rel` values are allowed (OKF flags as info).## Done when- Frontmatter `links` entry exists on the source- Body contains a Markdown link to the target- Log updated when a new edge is created

Frequently asked questions