CtrlK
BlogDocsLog inGet started
Tessl Logo

meta-github-pr-watch-digest

Inspect the user's open GitHub PRs / failing CI / new issues via `gh`, summarize into 3 buckets (to-review / awaiting-me / CI-red), and persist follow-ups to memory.

63

Quality

75%

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 ./src/opensquilla/skills/exp/meta-github-pr-watch-digest/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.

A concise, well-structured meta-skill body with concrete fallback commands, but the workflow lacks validation checkpoints and the fallback omits a command for surfacing new comments/issues.

Suggestions

Add a verification step before persisting (e.g., confirm the digest is non-empty / within max_words before calling memory_save) to introduce a feedback checkpoint.

Include a concrete gh command or filter for new comments/issues (e.g., 'gh pr view --comments' or a search query) so the fallback fully covers the three buckets.

Make the primary pull → digest → memorize sequence explicit in the body rather than relying solely on frontmatter composition.

DimensionReasoningScore

Conciseness

The body is lean — 'pulls open PRs / failing CI / new comments via the `github` skill (gh CLI), digests into three actionable buckets, and records follow-ups to long-term memory' — with no over-explanation; every token earns its place.

5 / 5

Actionability

The fallback gives concrete executable commands ('gh pr list', 'gh run list --status failure', 'memory_save'), but a command for fetching new comments/issues is missing and 'summarize' is left implicit.

4 / 5

Workflow Clarity

The pull → digest → memorize sequence is present (in frontmatter composition plus the body summary) but there are no validation checkpoints, which caps this batch-aggregating workflow at 3.

3 / 5

Progressive Disclosure

This is a sub-50-line skill with no external references needed; the body is well-organized into a concise overview and a clearly labeled Fallback section, meeting the simple-skill exception.

5 / 5

Total

17

/

20

Passed

Description

71%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.

A specific, distinct description that clearly states what the skill does and names concrete actions, but it omits any explicit 'when to use' trigger guidance, which caps completeness.

Suggestions

Add an explicit 'Use when...' clause naming trigger phrases (e.g., 'Use when the user asks for a PR digest, to review their open PRs, or check failing CI').

Include common synonyms such as 'pull requests' and 'checks' alongside 'PRs' and 'CI' to broaden natural-term coverage.

DimensionReasoningScore

Specificity

Quotes 'Inspect the user's open GitHub PRs / failing CI / new issues via `gh`', 'summarize into 3 buckets (to-review / awaiting-me / CI-red)', and 'persist follow-ups to memory' — three concrete, distinct actions with comprehensive coverage of the skill's purpose.

5 / 5

Completeness

The 'what' is clear (inspect, summarize, persist) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Natural terms 'GitHub PRs', 'failing CI', and 'new issues' are present, but synonyms like 'pull requests', 'checks', and 'comments' are missing, placing it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The GitHub PR-triage/digest framing with named buckets is a clear niche, but there is minor overlap risk with a general-purpose github skill.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
TokenRhythm/opensquilla
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.