Share a runnable prototype using the user's preferred deployment tool.

Quality

64%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/opencode/src/skill/builtin/.bundle/product-design/workflows/share/SKILL.md

Quality

Content

75%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.

The body is a compact, well-organized instruction skill with a clear gated workflow and useful guardrail rules. Its main gaps are the duplicated tool-unavailable sentence, the absence of any concrete deployment command or failure-recovery step, and reliance on external files that are not part of the bundle.

Suggestions

Remove the verbatim duplication of the tool-unavailable instruction between Workflow step 5 and the Rules, stating it once.

Add a brief failure-recovery step for the workflow, e.g. what to check and report when the deployment command errors or the returned URL does not load.

Give one concrete example of running a deployment or verifying the returned URL (e.g. fetch the URL and confirm a 200 response) to strengthen actionability.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanations, but the sentence 'If the selected tool is not available, say that clearly and ask whether to use another target' is duplicated verbatim in Workflow step 5 and the Rules, which could be trimmed.	4 / 5
Actionability	The guidance is concrete for an instruction-only skill, including a copy-ready question ('Where should I deploy this: @Sites, @Vercel, or another target?') and explicit rules, but 'Run the deployment when possible' provides no concrete command or example.	4 / 5
Workflow Clarity	The 8-step sequence is clearly ordered and confirmation-gated with a validation rule ('Do not claim the prototype is shared until you have a working URL'), but there is no explicit error-recovery loop for a failed deployment, only the tool-unavailable path.	4 / 5
Progressive Disclosure	The short body is organized into clear sections (Critical Overrides, User Context, Workflow, Rules) with one-level-deep signaled references, but the referenced paths (../index/SKILL.md, ../user-context/SKILL.md, ../../references/critical-overrides.md) live outside the skill bundle and are unverifiable.	4 / 5
	Total	16 / 20 Passed

Description

53%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.

The description states a clear, single-purpose capability but omits any 'when to use' trigger guidance, which limits discoverability and completeness. Keywords are relevant but thin on synonyms. Adding an explicit trigger clause would lift the two weakest dimensions.

Suggestions

Add a 'Use when...' trigger clause, e.g. 'Use when the user asks to share, publish, deploy, or get a link to a runnable prototype.'

Include natural trigger synonyms such as 'deploy', 'host', 'publish', and 'share link' alongside 'share' and 'prototype' to improve keyword coverage.

Name the concrete actions performed (confirm target, run deployment, return shareable URL) to raise specificity from 1-2 actions toward several specific actions.

Dimension	Reasoning	Score
Specificity	"Share a runnable prototype using the user's preferred deployment tool" names the domain (prototype deployment) and one or two actions (share/deploy) but does not list several concrete actions, matching the 1-2 concrete actions anchor rather than the several-actions anchor.	3 / 5
Completeness	The 'what' is clear (share/deploy a runnable prototype via the user's preferred tool), but there is no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	"Share" and "runnable prototype" are natural user terms, but common variations users would say ("deploy this", "host", "publish", "put it online") are missing, so keyword coverage is partial rather than good.	3 / 5
Distinctiveness Conflict Risk	The prototype-sharing niche is mostly distinct, with only minor overlap risk against generic deploy/hosting skills; it is not a 5 because the description lacks concrete distinct trigger phrases.	4 / 5
	Total	13 / 20 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
relative_links	Relative link issues: 3 suspicious	Warning

	Total	15 / 16 Passed

Repository: XiaomiMiMo/MiMo-Code
Path: packages/opencode/src/skill/builtin/.bundle/product-design/workflows/share/SKILL.md
Commit: f0293bf

Reviewed: 2 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.