_shared

Provides shared evidence profiles and skill routing references for the devkit skill suite.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/JonusNattapong/A2A-MCP --skill shared-jonusnattapong
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: _shared
Source: https://github.com/JonusNattapong/A2A-MCP/tree/main/src/agenttalk/skills/devkit/_shared
Command: npx skills add https://github.com/JonusNattapong/A2A-MCP --skill shared-jonusnattapong

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Multi-agent development teams suffer from false consensus, where agents approve work without executed evidence and duplicate shallow reviews masquerade as independent coverage. This reference bundle gives every devkit skill a single canonical source for typed evidence output profiles and a task-to-skill routing index so agents emit consistent, verifiable results. ## Core Features & Use Cases - Canonical Evidence Profiles: Defines the required fields for planning-artifact, production-handoff, review-result, qa-result, close-ack, and na-result outputs, marking each field as bus-validated or skill-policy. - Skill Routing Index: Maps tasks (new code, refactor, CI fix, QA strategy, reviews, release close) to the correct devkit skill, with negative triggers, capacity guidance, and dual review-mode rules. - Use Case: A lead agent closing a release milestone reads the routing index to assign review lenses, then each reviewer emits a review-result whose bus-validated fields (risk_class, release_blocker, tests_executed, evidence) pass the agenttalk gate validator. ## Quick Start Read the routing reference to pick the right devkit skill for your task, then follow the evidence profile for that skill when emitting your result.

Frequently Asked Questions about _shared

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

FAQPage Schema
How do I choose the right devkit skill for a task?▼

Read the routing index in references/routing.md, which maps tasks to skills: craft-code for new production code, refactor-code for behavior-preserving cleanup, fix-ci for failing checks, and qa-strategy for deciding test coverage. It also lists negative triggers describing when not to use each skill.

What fields are required in a review-result evidence profile?▼

A review-result requires bus-validated fields risk_class, release_blocker, tests_referenced, tests_executed, residual_risk, and evidence or artifacts, plus skill-policy fields status, reviewed_ref, and scope. The bus validator enforces the typed fields only when status is approved.

Can I invoke the _shared skill directly?▼

No, _shared is a reference holder, not an invocable capability skill. It exists only to bundle evidence.md and routing.md so other devkit skills can link to them via relative paths at the install location.

What is the difference between bus-validated and skill-policy fields?▼

Bus-validated fields are enforced by agenttalk code today, such as the named keys and allowed values checked by gates.validate_review_result_evidence. Skill-policy fields like reviewed_ref and scope are required by the skill contract and lead process but not enforced by the bus.

When should I use a fresh-context reviewer instead of a standing reviewer?▼

Use fresh-context reviewers for high-risk final-SHA verification, changes touching gate, close, security, or evidence-schema behavior, and large final diffs where continuity may bias. A fresh approval is evidence only and never counts as a close signoff.