fraimz

create a fraimz, make fraimz, prove it works, frame proof, PR proof, validate experience, e2e evidence, fraimz.html. The full fraimz loop — frame the claim, drive the real app via CDP, validate/repair, output fraimz.html. Use whenever a task ends with "please create a fraimz" or any change needs end-to-end proof.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable skill body with a clear validated workflow and good external referencing. It is slightly long and defers part of the API reference outward rather than bundling it.

Suggestions

Tighten the "Every fraimz is a demo" taxonomy and pitfall list to reduce length without losing the operational signal.

Inline a brief one-line summary of the most-used ctx.* helpers next to their names so the flow can be written without opening evals/README.md.

Consider bundling a minimal reference flow snippet under references/ so the headline API pattern is verifiable within the skill bundle.

Dimension	Reasoning	Score
Conciseness	Dense and operational with minimal over-explanation of concepts Claude already knows, though sections like the kind taxonomy and pitfall list add length that could be trimmed slightly.	4 / 5
Actionability	Provides concrete, copy-paste-ready commands (pnpm fraimz --flow, CDP launch, daytona script) and the headline ctx.prove API, with the full ctx.* reference deferred to evals/README.md rather than fully inlined.	4 / 5
Workflow Clarity	The loop is a clear six-step sequence with an explicit validate/repair/repeat feedback loop, a verdict step, and a pitfalls checklist for error recovery — exactly the checkpoint structure the anchor rewards.	5 / 5
Progressive Disclosure	Well-organized single-file overview with a clearly signaled "Source of truth" section pointing one level deep to evals/README.md and related repo paths; no skill bundle files exist to verify, so structure is judged on references.	4 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states both the capability and the trigger conditions with concrete phrases. The only weakness is minor redundancy in the opening keyword list.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions of the loop ("frame the claim, drive the real app via CDP, validate/repair, output fraimz.html"), though the opening "create a fraimz, make fraimz" is redundant padding keeping it just below comprehensive.	4 / 5
Completeness	Explicitly answers both what ("The full fraimz loop — frame the claim, drive the real app via CDP, validate/repair, output fraimz.html") and when ("Use whenever a task ends with 'please create a fraimz' or any change needs end-to-end proof") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good coverage of natural trigger phrases and synonyms ("please create a fraimz", "prove it works", "e2e evidence", "PR proof", "end-to-end proof", "fraimz.html"), but all terms orbit a single coined concept rather than a broad vocabulary.	4 / 5
Distinctiveness Conflict Risk	"fraimz" is a coined, distinctive term with a clear niche and explicit unique triggers, giving minimal conflict risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Devin-AXIS/iPolloWork
Path: .opencode/skills/fraimz/SKILL.md
Commit: 98deb63

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.