CtrlK
BlogDocsLog inGet started
Tessl Logo

wiki-log

Show recent entries from the LLM Wiki log (wiki/log.md). Uses the standardized

56

Quality

64%

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 ./.gemini/skills/wiki-log/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 concise, actionable, and well-structured for a simple read-only command skill, with executable examples and clear sections; minor gaps in spelling out filtered command variants and the canonical-copy pointer keep it just below top marks.

DimensionReasoningScore

Conciseness

The body is lean, assumes competence, and avoids explaining what grep/tail or a log file is; only minor sentences in 'What it does' and 'Scripts' (e.g. 'that's the point of the standardized header format') could be trimmed, matching the 'efficient; minor instances of over-explanation' anchor.

4 / 5

Actionability

It provides a copy-paste-ready core command ('grep "^## \[" wiki/log.md | tail -N') plus concrete usage examples and sample output; the only gap is that the filtered variants (--op/--since) are described in prose rather than given as fully-formed executable commands, keeping it just below the 5 anchor.

4 / 5

Workflow Clarity

This is a simple single-purpose read-only skill with an unambiguous action (parse log.md and print matching entries), so the simple-skill exception applies; it lands at 4 rather than 5 because the compositing of op/date filters into the command is left implicit rather than shown as a concrete sequence.

4 / 5

Progressive Disclosure

Content is well-organized into clearly labeled sections and the single external pointer ('Skill Reference' to the parent SKILL.md) is one level deep and clearly signaled; it is just short of 5 because the bulk of the command lives in a separate canonical copy referenced only by a sync comment, introducing mild navigation friction.

4 / 5

Total

16

/

20

Passed

Description

53%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 is appropriately concise and third-person, but it lacks an explicit 'when to use' trigger clause and only partially surfaces its distinct capabilities.

Suggestions

Add an explicit trigger clause such as 'Use when the user wants to see recent LLM Wiki activity, review what changed, or check the latest log entries' to lift completeness above the 3 cap.

Surface the filtering capabilities as concrete actions in the prose (e.g. 'Show, filter by op type, and date-range recent wiki log entries') rather than only via the Usage flag list.

Include natural user phrasings/synonyms (e.g. 'wiki history', 'what changed in the wiki') so trigger-term coverage reaches common variations.

DimensionReasoningScore

Specificity

Names the domain ('LLM Wiki log') and one concrete action ('Show recent entries') plus the grep+tail mechanism, but does not enumerate the several distinct capabilities (filter by op, by date, last N) as actions in their own right — matching the '1-2 concrete actions, not comprehensive' anchor rather than the multi-action anchor at 4.

3 / 5

Completeness

The 'what' is clear ('Show recent entries from the LLM Wiki log'), but the 'when' is only weakly implied via the Usage line rather than an explicit trigger clause; per the judging guideline, a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords are present ('wiki log', 'recent entries', op names like ingest/query/lint), but there is no 'Use when...' phrasing and common natural variations ('show wiki history', 'what changed in the wiki') are missing, placing it at the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The '/wiki-log' command and 'LLM Wiki log' reference a clear, narrow niche with minimal overlap risk against other skills; it falls just short of the 5 anchor because the trigger phrasing is not distinctive enough to fully eliminate overlap with general wiki-browsing skills.

4 / 5

Total

13

/

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
alirezarezvani/claude-skills
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.