Orch Render
Implement one design ticket through render-checked slices at its view identities. The design pack's unit executor.
Install
$ agentstack add skill-danmcinerney-orchflows-orch-render ✓ 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.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-danmcinerney-orchflows-orch-render) 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: one claimed design [ticket](../../../contracts/work-item.md) naming its view, identity set, design language, accessibility bar, and render and capture commands; an isolated workspace at a clean baseline.
Slice the view so each slice is provable in one capture — one state, one breakpoint, one token application. Per slice: implement the least markup and style that honestly meets it; capture at the slice's identities and read the image — the capture is the check, source text proves nothing visual; reconcile every value to a token and its scale per the ticket's craft reference; run the ticket's deterministic checks. Commit each verified slice. Close by running the ticket's full completion test through orch-verify, capturing every covered identity.
Never: claim a visual result without a capture; hard-code a value a token already names; leave an enumerated state uncaptured; touch paths outside the ticket's write scope.
Return: the completed ticket per [work-item.md](../../../contracts/work-item.md)'s filing law, its evidence citing captures by identity.
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.