construct-card-edit

Edit knowledge card fields and metadata through the construct knowledge CLI.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/mabstruct/construct --skill construct-card-edit-mabstruct
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: construct-card-edit
Source: https://github.com/mabstruct/construct/tree/main/CONSTRUCT-CLAUDE-impl/claude/skills/construct-card-edit
Command: npx skills add https://github.com/mabstruct/construct --skill construct-card-edit-mabstruct

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping knowledge cards accurate over time requires careful, validated edits to fields like confidence, lifecycle, and epistemic type; manual edits risk schema violations and broken domain references. This Skill guides the agent to identify the right card, validate requested changes, and apply them through the construct knowledge CLI so contracts are enforced. ## Core Features & Use Cases - Guided card identification: Locate cards by ID or title, with disambiguation when multiple candidates match. - Schema-validated edits: Validate confidence (1-5), source tier, epistemic type, lifecycle, domains, categories, tags, and sources before applying changes. - CLI-enforced contracts: Apply edits via construct knowledge card edit with structured JSON output and automatic event logging. - Use Case: A user says "update the confidence of the transformer-architecture card to 4"; the Skill finds the card, validates the value, runs the CLI, and confirms the change. ## Quick Start Ask the agent to edit a card, for example: "Update the confidence of the retrieval-augmentation card to 4 and set its lifecycle to growing."

Frequently Asked Questions about construct-card-edit

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

FAQPage Schema
How do I edit a knowledge card's confidence or lifecycle?▼

Tell the agent which card and which field to change, for example "update confidence of card X to 4". The Skill validates the value and applies it via the construct knowledge card edit CLI command.

How does the skill find which card to edit?▼

It looks up cards by ID in the cards directory or searches card files by title. If multiple cards match, it lists the candidates and asks you to pick one before making changes.

What validation happens before a card edit is applied?▼

Confidence and source tier must be integers 1-5, epistemic type and lifecycle must be valid enums, and domain and category references must exist in domains.yaml. Lifecycle promotions and archiving also trigger governance checks.

What happens if the card edit CLI command fails?▼

The Skill displays the structured error from the CLI, including the field, reason, and suggestion, and offers a retry. The card file is left unchanged when validation fails.

Does archiving a card remove its connections to other cards?▼

No. Archiving changes only the lifecycle field; connections to other cards are preserved. The Skill notes this explicitly when a lifecycle change to archived is applied.