clickclack

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

Quality

77%

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

92%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 an excellent lean ops runbook: executable commands, a clearly sequenced deploy workflow with a critical rollout gotcha, and a concrete verification section. Only minor conciseness room exists around the inline account/zone identifiers.

Dimension	Reasoning	Score
Conciseness	Dense and operational with no concept padding (no explanations of Cloudflare/Docker), though inline account/zone IDs and 1Password item names are raw metadata that could arguably live in a reference file.	4 / 5
Actionability	Fully executable, copy-paste-ready commands with concrete values (exact git/wrangler/pnpm commands, URLs, container UUID, and a precise grep pattern) covering the common deploy and verify cases.	5 / 5
Workflow Clarity	Deploy is a clear 5-step numbered sequence with an explicit rollout gotcha (error-recovery guidance) and a dedicated Verify section serving as the validation checkpoint; validation is present so the destructive-op cap does not apply.	5 / 5
Progressive Disclosure	Under 50 lines, single-purpose, with no bundle files needed and well-organized sections (What/Prod/Deploy/Verify/Guardrails), meeting the simple-skill exception for a top score on progressive disclosure.	5 / 5
	Total	19 / 20 Passed

Description

62%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 is specific and highly distinct, tied to a named product niche, but it lacks an explicit 'Use when...' trigger clause and relies on proper-noun keywords rather than natural user phrases. Adding a trigger clause and a couple of synonyms would lift completeness and trigger_term_quality.

Suggestions

Add an explicit 'Use when ...' clause, e.g. 'Use when deploying ClickClack, checking the hosted app, or resolving clickclack.chat DNS/docs questions.'

Include a few natural synonyms users might say beyond the product name, such as 'ClickClack deploy', 'roll out the ClickClack container', or 'clickclack.chat downtime'.

Consider naming one or two more granular concrete actions (e.g. 'bump container version, verify build hash') to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the ClickClack ops domain and lists several concrete action areas ('Cloudflare Workers deploy, DNS/docs/app, container rollout'), with only minor gaps in granular coverage.	4 / 5
Completeness	Provides a clear 'what' (the ops areas) but includes no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Contains relevant domain terms ('deploy', 'container rollout', 'DNS/docs/app') a user might say, but relies heavily on the product proper noun and lacks common variations or synonyms.	3 / 5
Distinctiveness Conflict Risk	Scoped to a specific named product (ClickClack) with distinct deploy/runtime surfaces, giving it a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	15 / 20 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: 92442a1

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.