accint-solve

Route a goal through acc's scored-memory loop via acc_act(runtime="solve"); deliberate any returned brain_frame and submit via continue.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

100%

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

The body is a tight, actionable routing guide with a clear sequenced workflow and explicit command signatures, well-suited to a simple single-purpose skill. Its only soft spot is the description-level jargon, which the content itself cannot fix.

Dimension	Reasoning	Score
Conciseness	Lean and efficient — every line (the two MCP verbs, the numbered routing steps, the PREDICT format) earns its place; domain terms are load-bearing, not padding.	3 / 3
Actionability	Gives concrete, near-copy-paste command signatures ('acc_act(runtime="solve", input=...)' and the continue call with frame_id/submit_token/proposal_text) plus the exact 'PREDICT: <0.00-1.00> <why>' suffix format.	3 / 3
Workflow Clarity	A clearly sequenced 1–6 workflow with a feedback loop (brain_frame → deliberate → continue → outcome) and explicit invariants ('never leave a frame unresolved'); the operation is routing, not destructive/batch, so no validation checkpoint is required.	3 / 3
Progressive Disclosure	A simple, single-purpose skill under 50 lines with well-organized sections (When to Use, Limitations) and no need for external references, which meets the simple-skill bar for a top score.	3 / 3
	Total	12 / 12 Passed

Description

52%

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

The description is specific and distinct but reads as internal jargon rather than user-facing triggers, and it omits an explicit 'Use when' clause. Rewording around natural terms and adding a trigger condition would lift completeness and trigger quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to run a goal through acc's solve runtime or continue a paused brain_frame'.

Soften jargon by pairing technical terms with natural phrasing (e.g. 'solve a goal via acc', 'continue a paused deliberation') so users can summon it with everyday words.

Lead with the user-facing capability before the runtime mechanics to improve trigger-term quality.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Route a goal through acc's scored-memory loop', 'deliberate any returned brain_frame', 'submit via continue' — each tied to a specific verb/construct.	3 / 3
Completeness	Clearly answers what the skill does, but provides no explicit 'Use when...' trigger clause; per guidelines a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Relies on technical jargon ('scored-memory loop', 'brain_frame', 'acc_act(runtime="solve")') that a user would not naturally say when reaching for this skill.	1 / 3
Distinctiveness Conflict Risk	Tied to a distinct niche (acc's solve runtime and brain_frame protocol), making it unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: 6e69f00

Reviewed: 5 days 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.