CtrlK
BlogDocsLog inGet started
Tessl Logo

github-cache-hygiene

GitHub quota/cache hygiene: Gitcrawl archives, Octopool-backed gh, freshness, limits.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/github-cache-hygiene/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%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 skill body is exemplary: lean, fully executable, and clearly sequenced with concrete commands and CI-polling discipline. The only gap is the absence of an explicit validation/retry feedback loop for batch and write operations, which caps workflow clarity at 4.

Suggestions

Add an explicit validate-fix-retry loop for batch/write operations (e.g. after a write, verify the readback and retry on mismatch before proceeding).

Consider splitting the dense command catalogue into a reference file if the body grows, keeping SKILL.md as an overview.

DimensionReasoningScore

Conciseness

The body is lean and command-driven, assumes Claude's competence, and every explanatory sentence earns its place with no concept padding.

5 / 5

Actionability

It provides fully executable, copy-paste-ready gitcrawl/gh/octopool commands covering the common discovery, read, write, and CI-polling cases.

5 / 5

Workflow Clarity

The archive-first then bare-gh sequence is clear with CI-polling intervals and a targeted-readback checkpoint, but it lacks an explicit validate-fix-retry feedback loop for batch/write operations.

4 / 5

Progressive Disclosure

Content is organized into clear, well-signaled sections (Default Path, Freshness, Octopool, Agent Etiquette) with no nested references and no bundle files needed.

5 / 5

Total

19

/

20

Passed

Description

58%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 well-scoped to a distinct internal niche, but it omits explicit 'when to use' trigger guidance and leans on project jargon rather than natural user phrasing. Adding a 'Use when...' clause with common trigger terms would raise completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when ...' clause naming natural triggers (e.g. 'Use when hitting GitHub rate limits, repeated gh calls, or stale local GitHub data').

Replace some internal proper nouns with common synonyms users actually say (e.g. 'GitHub API rate limits', 'gh caching') alongside Gitcrawl/Octopool.

Frame capabilities as verbs (e.g. 'Discover, read, and refresh GitHub issue/PR data') to sharpen specificity.

DimensionReasoningScore

Specificity

Names the domain and several concrete components ('Gitcrawl archives, Octopool-backed gh, freshness, limits') with minor gaps in action-verb framing, fitting the 'several specific actions; minor gaps' anchor.

4 / 5

Completeness

A clear 'what' is present (named mechanisms for quota/cache hygiene) but there is no 'Use when...' trigger clause, so per the cap it sits at 'clear what, when missing or weakly implied'.

3 / 5

Trigger Term Quality

Keywords like 'GitHub quota/cache hygiene' and 'Octopool-backed gh' are relevant but lean on project-internal jargon over natural user phrases, matching 'some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

The Gitcrawl/Octopool niche is mostly distinct with only minor overlap risk against closely related GitHub skills.

4 / 5

Total

14

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
steipete/agent-scripts
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.