Run any Skill in Manus with one click

finish-the-loop

Stars17

Forks0

UpdatedJuly 16, 2026 at 05:30

Close implementation loops with target-bound independent evidence and a portable proof receipt. Use when an agent changes a real system and must earn a completion claim that survives the session.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

zakelfassi

zakelfassi/skills-driven-development

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	finish-the-loop
description	Close implementation loops with target-bound independent evidence and a portable proof receipt. Use when an agent changes a real system and must earn a completion claim that survives the session.

Finish the Loop

Treat completion as a claim that needs evidence from the intended target.

Read WORKFLOW.json and create .skdd/runs/<run-id>/state.json before changing the system.
Pin each acceptance line to an explicit target tuple: environment, resource, and revision. Do not let the executor silently choose or revise the target.
Record the executor identity and credential scope.
Reproduce, change, and drive the real artifact. Keep the run state resumable after interruption.
Collect evidence with a provider that has a different identity and credential scope from the executor. A test run by the same process is useful feedback, but it is not independent proof.
Emit receipt.json using the proof-receipt schema. Bind the skill bytes and each acceptance contract with SHA-256 digests.
Run skdd proof verify receipt.json --skill SKILL.md.
Report verified only when the verifier passes. Otherwise report the reason codes and leave the loop refused, blocked, or open.

Never translate “the build passed” into “the user-visible outcome works.” Evidence must match the acceptance target exactly.

More from this repository

same repository

alpha-skill

zakelfassi/skills-driven-development

First fixture skill for skdd add tests. Use when testing drop installation.

2026-07-0217

beta-skill

zakelfassi/skills-driven-development

Second fixture skill for skdd add tests. Use when testing multi-skill drops.

2026-07-0217

backfill-runbook

zakelfassi/skills-driven-development

Safely backfill historical data for a pipeline stage — scope the date range, run a dry-run, execute in chunks to avoid overwhelming the database, and verify row counts after each chunk. Use when historical data is missing, when a pipeline stage is added retroactively, or when asked to "backfill the {stage} table from {start_date}".

2026-06-1217

data-quality-gate

zakelfassi/skills-driven-development

Add or extend data validation checks in the pipeline when data quality issues are detected — null-percentage thresholds, value ranges, referential integrity, and row-count sanity checks. Use when a pipeline breaks on bad data, when onboarding a new dataset, or when asked to "add a quality check for {column}".

2026-06-1217

dataset-onboard

zakelfassi/skills-driven-development

Onboard a new raw dataset into the data platform — sniff the schema, generate a profiling notebook, create the ingestion job, and add an entry to the data dictionary. Use when adding a new data source, when a partner delivers a new CSV/Parquet drop, or when asked to "onboard the {name} dataset".

2026-06-1217

experiment-log

zakelfassi/skills-driven-development

Record a model training run — log parameters, metrics, and artifact paths, then append a structured row to the experiments ledger. Use when a training run completes, when asked to "log this experiment", or when comparing runs to decide which model to promote.

2026-06-1217

name	finish-the-loop
description	Close implementation loops with target-bound independent evidence and a portable proof receipt. Use when an agent changes a real system and must earn a completion claim that survives the session.

Finish the Loop

Treat completion as a claim that needs evidence from the intended target.

Read WORKFLOW.json and create .skdd/runs/<run-id>/state.json before changing the system.
Pin each acceptance line to an explicit target tuple: environment, resource, and revision. Do not let the executor silently choose or revise the target.
Record the executor identity and credential scope.
Reproduce, change, and drive the real artifact. Keep the run state resumable after interruption.
Collect evidence with a provider that has a different identity and credential scope from the executor. A test run by the same process is useful feedback, but it is not independent proof.
Emit receipt.json using the proof-receipt schema. Bind the skill bytes and each acceptance contract with SHA-256 digests.
Run skdd proof verify receipt.json --skill SKILL.md.
Report verified only when the verifier passes. Otherwise report the reason codes and leave the loop refused, blocked, or open.

Never translate “the build passed” into “the user-visible outcome works.” Evidence must match the acceptance target exactly.