원클릭으로 Manus에서 모든 스킬 실행

askit-build-chain-contract

스타1

포크0

업데이트2026년 6월 3일 14:37

Creates and improves a plugin's chain contract (agents/_chain-permitted.yaml) to the Advanced Skill Library Standard. Use when a skill or subagent invokes another component and you need to declare the permitted inter-component invocations, or to resolve S4 orphan or phantom findings.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

product-on-purpose

product-on-purpose/agent-skills-toolkit

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

관련 직업SOC

SOC 직업 분류 기준

소프트웨어 개발자컴퓨터 및 수학직·SOC 15-1252

파일 탐색기

3 개 파일

SKILL.md

readonly

이 저장소의 다른 Skills

같은 저장소

askit-build-skill

product-on-purpose/agent-skills-toolkit

Creates and improves agentskills.io skills to the Advanced Skill Library Standard. Use when you need to author a new SKILL.md, scaffold a skill directory, or raise an existing skill's conformance and description quality.

2026-06-121

askit-evaluate

product-on-purpose/agent-skills-toolkit

Evaluates a skill or plugin against the Advanced Skill Library Standard across three modes, producing deterministic conformance findings and a tier, an opt-in behavioral pass, and a qualitative review. Use when you want to audit conformance, judge whether a skill behaves and triggers correctly, get a qualitative review, or see what blocks the next tier.

2026-06-121

linkrot

product-on-purpose/agent-skills-toolkit

Converts a meeting transcript into a decision log. Use when the user asks to extract decisions, action items, or owners from a transcript.

2026-06-121

askit-migrate

product-on-purpose/agent-skills-toolkit

Assesses an existing skills repository against the Advanced Skill Library Standard, produces a staged bring-to-conformance plan, and writes the minimal canonical manifest so the repo becomes gradeable. Use when adopting a foreign or ad-hoc skills repo, migrating a Claude-only plugin toward cross-agent conformance, or planning a Bronze-to-Silver upgrade path.

2026-06-051

askit-release

product-on-purpose/agent-skills-toolkit

Builds and validates a plugin's release by computing the version, promoting the changelog, curating the release notes, and running the readiness gate, to the Advanced Skill Library Standard. Use when cutting a release, bumping the plugin version, updating the changelog or release notes, or checking release readiness.

2026-06-051

askit-backlog

product-on-purpose/agent-skills-toolkit

Creates, triages, and prunes a plugin's two backlogs (new-component proposals and enhancements) to the Advanced Skill Library Standard. Use when capturing a new-component proposal through the why-gate, prioritizing backlog items, or removing stale or completed entries.

2026-06-031

name	askit-build-chain-contract
description	Creates and improves a plugin's chain contract (agents/_chain-permitted.yaml) to the Advanced Skill Library Standard. Use when a skill or subagent invokes another component and you need to declare the permitted inter-component invocations, or to resolve S4 orphan or phantom findings.
metadata	{"version":"0.1.0","tier":"universal","audience":"advanced"}

askit-build-chain-contract

Purpose

Author a plugin's chain contract: the explicit declaration of which components may invoke which others (Standard sec 3.6). A chain contract is a CONDITIONAL MUST - required if and only if a component invokes another, so a plugin with no inter-component invocation ships no contract (no empty governance files). Two modes: create authors agents/_chain-permitted.yaml (and the optional agents/_pairing.yaml); improve resolves S4 findings. Authoring depth is in references/authoring-chain-contracts.md. Follows the shared builder contract (../../docs/reference/builder-pattern.md).

When to use

When a skill or subagent declares a chain: to another component and you need to permit it, or when evaluate reports an S4 orphan (an invocation not permitted) or phantom (a contract entry naming a missing component).

create mode

Scan components for chain: declarations (which caller invokes which callees). Skip the contract entirely if nothing chains (the conditional MUST).
Author agents/_chain-permitted.yaml: one entry per caller, listing the components it may invoke. Copy templates/chain-permitted.yaml if none exists.
Optionally author agents/_pairing.yaml for recommended (not required) skill plus subagent pairings.
Evaluate (node scripts/evaluate.mjs . --json) until S4 is clean: every chain: invocation is permitted (no orphan) and every contract entry names an on-disk component (no phantom).

improve mode

Run node scripts/evaluate.mjs . --json and read the S4 findings.
For an orphan, add the missing caller: [callee] permission. For a phantom, fix the misspelled name, remove the stale entry, or create the missing component.
Re-run to confirm S4 is clean.

Scope

The contract is agent-agnostic: one agents/_chain-permitted.yaml (no per-target form). It binds exactly when there is an invocation to make safe (sec 3.6), so it is a safety mechanism, not ceremony. S4 (chain-contract integrity) flags orphans and phantoms; do not ship an empty contract for a plugin that does not chain.