construct-card-evaluate

Evaluates knowledge cards for lifecycle promotion by invoking the Python card.evaluate gate.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deciding which knowledge cards should be promoted from seed to growing to mature is a judgment-heavy task that drifts when re-implemented in prompts. This Skill delegates that judgment to a single tested Python promotion gate, so promotion decisions stay consistent and reviewable. ## Core Features & Use Cases - Promotion Gate Invocation: Runs construct card evaluate (or the MCP equivalent) against a workspace to produce one PromotionDecision per non-mature card. - Decision Presentation: Groups decisions into promote, hold, and escalate, surfacing the method field so failure-driven escalations (rule-based) are distinguishable from genuine borderline calls (llm-judgment). - Read-Only Evaluation: Proposes decisions without writing lifecycle changes; approved promotions flow through the reviewed curation path. - Use Case: During a curation cycle, ask the agent to check promotions; it runs the gate and returns a summary such as "3 promote, 5 hold, 2 escalate (1 borderline, 1 evaluation failure)" for your review. ## Quick Start Ask the agent to evaluate cards and check which ones are ready for promotion in the current workspace.

Frequently Asked Questions about construct-card-evaluate

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

FAQPage Schema
How do I evaluate cards for promotion in CONSTRUCT?▼

Run `construct card evaluate --workspace . --json` or ask the agent to check promotions. The gate returns one PromotionDecision per non-mature card, grouped as promote, hold, or escalate, without writing any changes.

What is the difference between rule-based and llm-judgment escalations?▼

A rule-based escalation means the LLM evaluation failed and retried out, so the card was mechanically escalated and usually just needs a re-run. An llm-judgment escalation is a genuine borderline case the model reasoned about, which warrants human review.

Does card evaluation write lifecycle changes directly?▼

No. The evaluation is read-only and only proposes PromotionDecisions. Approved promotions are applied through `construct curation review` behind a human gate during a curation run.

Can I run card evaluation through MCP instead of the CLI?▼

Yes. Start the server with `construct mcp` and invoke the `construct_card_evaluate` tool with a workspace_path argument. It calls the same Python promotion gate as the CLI.

Why did my card evaluation escalate everything unexpectedly?▼

Mass rule-based escalations typically indicate the LLM provider was unreachable or misconfigured, causing evaluations to fail and retry out. Check the provider configuration and re-run the gate rather than treating these as borderline judgments.