Install
$ agentstack add skill-danmcinerney-orchflows-orch-review-fix ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Require: a fixed result identity; the stamped lens or lenses; the pack's oracle policy; the spec; the standards owner by pointer, where the workspace names one; the pack's craft reference; the write scope the repair may touch.
Dispatch one read-only reviewer lane per lens, each its own delegation packet over the same fixed revision, directly through orch-delegate — each lane applies its lens via orch-critique or the lens's named skill against the spec, the standards owner by pointer, and the craft reference, criteria restated fresh from the spec, in a context independent of whoever produced the revision; each lane's result crosses orch-integrate as it lands. Once every lane has landed, adjudicate the findings' combined content into the combined validated set, grouped by shared cause per [rules/verification.md](../../../rules/verification.md) §9 — cross-lens inconsistency is a finding of its own. Spend at most one correction pass through orch-repair, naming the orch-worker profile, bounded to the write scope, on the combined validated set. Close with one orch-verify over the affected criteria.
Never: a second correction pass (survivors return as findings); one gate per lens or per domain; a reviewer lane that edits.
Return: validated findings with dispositions, the correction's changed artifacts, anything repair queued, and the final verification.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: DanMcInerney
- Source: DanMcInerney/orchflows
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.