CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.clacky/skills/oss-upload/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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 lean, fully executable reference: concrete commands, real examples for the common cases, and clean section organization appropriate to a simple single-purpose skill. The only meaningful gap is the absence of a post-upload verification step, which matters given the recursive batch upload example.

DimensionReasoningScore

Conciseness

The body is lean with no explanations of concepts Claude already knows, but the bucket name and the public URL pattern each repeat three times across Bucket Info, Upload Command/Public URL, and Steps — minor redundancy that could be trimmed, matching the 'efficient; minor instances of over-explanation' anchor.

4 / 5

Actionability

"coscli cp <local-file> cos://clackyai-1258723534/<remote-path>" plus three concrete, copy-paste-ready examples covering a single file, a subdirectory target, and a recursive directory upload fully match the 'copy-paste ready commands covering common cases' anchor.

5 / 5

Workflow Clarity

The Steps section gives a clear sequence with a pre-check ("Confirm local file exists") but no post-upload verification such as confirming the object is accessible at the public URL. Because the skill includes a batch operation (recursive "-r" upload) without a validation/verification step, workflow clarity is capped at 3 per the batch-operation rule.

3 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, references no external files (and none are needed), and is organized into clear sections (Tool, Bucket Info, Upload Command, Public URL, Steps), matching the simple-skill exception for a top progressive-disclosure score.

5 / 5

Total

17

/

20

Passed

Description

70%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 clearly states what the skill does and when to use it, with an explicit "Use when" clause and mostly natural trigger terms. Its main weakness is narrow capability coverage — a single upload action with limited trigger synonyms — which leaves specificity and completeness slightly above the midpoint rather than excellent.

Suggestions

Broaden the capability list in the description (e.g., mention uploading single files or entire directories recursively, and retrieving the resulting public URL) to raise specificity beyond a single action.

Add natural trigger synonyms to the "Use when" clause, such as "publish a file", "get a public link/URL for a file", or "host static files", to improve both trigger coverage and completeness.

Clarify the scope boundary (e.g., this skill is specifically for the clackyai Tencent COS bucket / oss.1024code.com CDN, not general cloud storage) to further reduce overlap with generic deploy/upload skills.

DimensionReasoningScore

Specificity

"Upload local files to Tencent COS (oss.1024code.com CDN) using coscli" names the domain and one concrete action (upload via a named tool), matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor; it does not list additional capabilities (listing, deleting, syncing) that would reach anchor 4.

3 / 5

Completeness

Both parts are explicit: a clear "what" (upload local files to Tencent COS using coscli) and an explicit "Use when user wants to upload a file to CDN/OSS, or deploy static assets" clause with concrete triggers. It sits between anchors 4 and 5 because the trigger set is narrow — no synonym triggers — so it is above the midpoint but short of the comprehensive anchor-5 example.

4 / 5

Trigger Term Quality

Includes several natural phrases a user would say — "upload a file", "CDN/OSS", "deploy static assets" — giving good keyword coverage, though common synonyms like "publish", "host", or file-type triggers are missing, keeping it below the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The description is tied to a specific bucket, CDN host, and the coscli tool, making it mostly distinct; minor overlap risk remains with generic deploy/publish skills via the "deploy static assets" trigger, so it is not the clear-niche anchor 5.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Reviewed

Table of Contents

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.