oss-upload

Upload local files to Tencent COS (oss.1024code.com CDN) using coscli. Use when user wants to upload a file to CDN/OSS, or deploy static assets.

Quality

73%

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 ./.clacky/skills/oss-upload/SKILL.md

Quality

Content

72%

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

A concise, highly actionable single-purpose skill with executable commands and concrete examples, well-organized for its size. The main gaps are minor redundant restatements and a missing post-upload verification step for the overwrite operation.

Suggestions

Add a post-upload verification checkpoint to the workflow, e.g. check the `coscli cp` exit status or `curl -I` the resulting public URL before reporting success, to satisfy the feedback-loop expectation for state-changing uploads.

Remove the redundant '## Public URL' section and the restated command in '## Steps' so the bucket info and command sections are the single sources of truth, tightening token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanations Claude already knows, but the public-URL pattern and the upload command are each restated across 'Bucket Info', '## Public URL', and '## Steps', which could be tightened. It is above 1 (no padding or background fluff) but below 3 because of the redundant restatements.	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands (`coscli cp <local-file> cos://clackyai-1258723534/<remote-path>`) plus three concrete examples with real paths and the recursive `-r` flag, matching the 'fully executable code/commands; specific examples; copy-paste ready' anchor. It is not a 2 because the commands are complete and concrete, not pseudocode.	3 / 3
Workflow Clarity	Steps are sequenced (confirm file exists -> run cp -> return URL), but for an overwrite/state-changing upload there is no post-upload verification checkpoint (e.g. checking the cp exit status or curling the public URL), capping it at 2 per the feedback-loop guidance. It is above 1 (a clear sequence with a pre-check exists) but below 3 due to the missing validation/feedback loop.	2 / 3
Progressive Disclosure	The skill is under 50 lines, single-purpose, needs no external references (none of references/scripts/assets exist), and is organized into clear sections (Tool, Bucket Info, Upload Command, Examples, Public URL, Steps), matching the simple-skills allowance for a 3. It is not a 2 because no content is inappropriately inlined or poorly signaled.	3 / 3
	Total	10 / 12 Passed

Description

75%

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 tight, third-person description that cleanly states both what it does and when to use it with an explicit trigger clause. Its main weaknesses are single-action specificity and slightly limited trigger-term coverage.

Suggestions

Broaden trigger-term coverage by adding common variations a user might say, e.g. 'upload files or images', 'host/publish static assets', so it captures more natural phrasings.

If the skill supports more than plain upload (e.g. listing, deleting, or syncing objects), enumerate those concrete actions to lift specificity toward multiple specific capabilities.

Dimension	Reasoning	Score
Specificity	Names a concrete domain and action ("Upload local files to Tencent COS ... using coscli") but lists only a single upload action rather than multiple specific concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor. It is not a 1 because the action and tool are explicit and concrete, not vague; it is not a 3 because no second distinct capability is enumerated.	2 / 3
Completeness	Clearly answers both what ("Upload local files to Tencent COS ... using coscli") and when via an explicit "Use when user wants to upload a file to CDN/OSS, or deploy static assets" trigger clause, matching the 'clearly answers both what AND when with explicit triggers' anchor. The presence of the explicit 'Use when...' clause avoids the cap at 2.	3 / 3
Trigger Term Quality	Includes natural phrasings a user would say ("upload a file to CDN/OSS", "deploy static assets") but coverage is thin and misses common variations such as "upload files/images", "host", or "publish". It is above 1 (terms are natural, not jargon-only) but below 3 (not comprehensive coverage).	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Tencent COS via the coscli tool to a specific CDN) with distinct triggers unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers; unlikely to conflict' anchor. It is not a 2 because the service/tool specificity makes overlap with other skills unlikely.	3 / 3
	Total	10 / 12 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: clacky-ai/openclacky
Path: .clacky/skills/oss-upload/SKILL.md
Commit: 4aea278

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