clickclack

ClickClack ops: chat app, Cloudflare Workers deploy, DNS/docs/app, container rollout.

Quality

78%

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 ./skills/clickclack/SKILL.md

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 content is a tightly written, highly actionable ops runbook with executable commands, a clear deploy sequence, explicit verification steps, and well-organized sections. It is an exemplar of lean, copy-paste-ready guidance.

Dimension	Reasoning	Score
Conciseness	The body is lean and dense with operational specifics, explaining no concepts Claude already knows; every section earns its place, matching anchor 3.	3 / 3
Actionability	It provides copy-paste-ready commands (git pull, open -a OrbStack, pnpm deploy:cloudflare, curl hash checks, wrangler containers info) with concrete IDs and naming conventions, matching anchor 3.	3 / 3
Workflow Clarity	Deploy is a clear numbered sequence paired with a dedicated Verify section containing explicit validation commands (hash comparison, container health), providing a feedback loop for a risky operation.	3 / 3
Progressive Disclosure	No external bundle files are needed and the body is well-organized into clear single-level sections (What, Prod, Deploy, Verify, Guardrails), which per the simple-skills note warrants a 3.	3 / 3
	Total	12 / 12 Passed

Description

57%

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 concise and identifies a clear niche with some concrete actions, but it omits an explicit trigger clause and leans on project jargon that limits natural trigger terms. Adding a "Use when..." clause with plain-language triggers would raise completeness and trigger_term_quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to deploy ClickClack, check the hosted app/domain, or roll out a new container image."

Replace jargon-heavy shorthand ("DNS/docs/app") with clearer natural-language phrases a user would actually say ("manage DNS records, docs site, and hosted app").

Spell out one or two more concrete actions (e.g. "bump the container image and verify the deploy hash") to move specificity toward anchor 3.

Dimension	Reasoning	Score
Specificity	Names a concrete domain and several actions ("Cloudflare Workers deploy, DNS/docs/app, container rollout") but uses terse abbreviations rather than a comprehensive list of specific actions, matching anchor 2.	2 / 3
Completeness	It answers what the skill does but lacks any explicit "Use when..." trigger clause, so per the guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	"Deploy" and "chat app" are natural user terms, but much of the description is project jargon ("ClickClack ops", "container rollout") without broad coverage of common variations, matching anchor 2.	2 / 3
Distinctiveness Conflict Risk	The named product "ClickClack ops" with its specific surface inventory defines a clear narrow niche unlikely to conflict with unrelated skills, matching anchor 3.	3 / 3
	Total	9 / 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: steipete/agent-scripts
Path: skills/clickclack/SKILL.md
Commit: bb36883

Reviewed: about 13 hours 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.