loop-execution-evaluator SKILL.md skillA
loop-execution-evaluator from ibrahim-3d/orchestrator-supaconductor is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ibrahim-3d/orchestrator-supaconductor/loop-execution-evaluator@git:20260312.c37221cPins git:20260312.c37221c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ibrahim-3d/orchestrator-supaconductor
- Path
skills/loop-execution-evaluator/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260312.c37221c, committed Mar 12, 2026
- First version recorded
- Feb 17, 2026
- Size
- 6,983 bytes
- Repository stars
- 380
- License
- AGPL-3.0
Evaluate-Loop Step 4: EVALUATE EXECUTION. This is the dispatcher agent — it determines the track type and invokes the correct specialized evaluator. Does NOT run a generic checklist. Instead dispatches to: eval-ui-ux (screens/design), eval-code-quality (features/infrastructure), eval-integration (APIs/auth/payments), eval-business-logic (generator/rules/state). Triggered by: 'evaluate execution', 'review implementation', 'check build', '/phase-review'. Always runs after loop-executor.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Loop Execution Evaluator — Step 4: Dispatcher This agent does NOT evaluate directly. It determines the track type and dispatches the correct specialized evaluator. ## Why Specialized Evaluators? Different track types need fundamentally different checks: - A **UI track** needs design system adherence, visual consistency, responsive checks - A **feature track** needs build integrity, type safety, code patterns - An **integration track** needs API contracts, auth flows, error recovery - A **business logic track** needs product rules, edge cases, state transitions A generic checklist misses critical issues specific to each type. ## Dispatch Logic read_file the track's `metadata.json` and `spec.md` to determine the track type, then dispatch: | Track Type | Keywords in spec/metadata | Evaluator | |-----------|--------------------------|-----------| | UI / Design | "screen", "component", "design system", "layout", "visual", "UI shell" | `eval-ui-ux` | | Feature / Code | "implement", "feature", "refactor", "infrastructure", "hook", "store" | `eval-code-quality` | | Integration | "Supabase", "Stripe", "Gemini", "API", "auth", "database", "webhook" | `eval-integration` | …
Read the whole file at its exact version.
How to install
mdr add ibrahim-3d/orchestrator-supaconductor/loop-execution-evaluator@sha256:f83034c83570c60bThe line at the top of this page pins the label git:20260312.c37221c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ouydiyjj6wsvb52w)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Feb 17, 2026 and Mar 12, 2026, about one every 23 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260312.c37221c latest | 2026-03-12 | c37221c | 6,983 B | A | view · diff |
| git:20260217.9cad9a5 | 2026-02-17 | 9cad9a5 | 6,948 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6983 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
ibrahim-3d/orchestrator-supaconductor · 380 stars · license AGPL-3.0 · pushed 2026-09-27 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_ouydiyjj6wsvb52w GET https://markdownregistry.com/api/v1/resolve?ref=ibrahim-3d/orchestrator-supaconductor/loop-execution-evaluator GET https://markdownregistry.com/api/v1/blob/f83034c83570c60b0436a5d3b66669bab4329292b1d27d9152a847a84eba3855
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.