CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

daily-oss

Batch processing issues, PRs, discussions, implementations, etc.

Quality

55%

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 ./.claude/skills/daily-oss/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 a dense, opinionated coordinator instruction set with excellent routing to real one-level-deep asset files and specific communication rules. Its weaknesses are redundancy between the Key Points and Lessons-learned sections, the absence of concrete message templates or commands, and no explicit validation checkpoints in the batch-processing flow. Consolidation and a feedback-loop step would lift it substantially.

Suggestions

Add an explicit validation checkpoint to the main flow (e.g. re-fetch PR/issue state and re-verify before each verdict and the final summary), which would also remove the workflow_clarity cap.

Move the Lessons-learned log to a reference file (e.g. assets/lessons-learned.md) and keep only the template plus a pointer in SKILL.md, removing the duplication with Key Points 11–14.

Include one concrete example of a compliant user-facing message (context + 5W1H proposal + question) so the communication rules are executable rather than descriptive.

DimensionReasoningScore

Conciseness

The body is mostly terse imperative rules that assume Claude's competence, but there is real redundancy: 'THERE IS NO URGENCY' is stated twice ('STOP RUNNING AHEAD. THERE IS NO URGENCY' and the closing urgency note), Key Points 11–14 restate the same communication rules, and several Lessons-learned entries duplicate body rules ('Questions carry the logic, never the mechanics' restates point 12). Mostly efficient but could be tightened — anchor 3, not 4 because the duplication is more than minor.

3 / 5

Actionability

Routing is genuinely concrete (exact asset paths, dependency ordering, just-in-time loading, subagent delegation rules) and the communication spec is specific (5W1H, <15 words per sentence). However the main body contains no commands, code, or message templates, and several directives remain abstract ('Diagnose the actual pain', 'ALWAYS DIG DEEPER'). Some concrete guidance but incomplete relative to the executable anchor — 3, not 4 because a reader cannot produce a compliant message without inventing the format themselves.

3 / 5

Workflow Clarity

A sequence exists (route by task type with an explicit priority order, delegate to subagents, report back one-by-one), and scattered rules act as partial checkpoints ('IF SOMETHING IS NOT DONE - IT IS NOT DONE', 'Re-check PR state before presenting'). But this is a batch-operation skill and the main flow lacks explicit validation checkpoints — per the rubric, missing validation in batch workflows caps workflow_clarity at 3. It is above anchor 2 because the routing sequence itself is well defined.

3 / 5

Progressive Disclosure

Four references (issues-review, issues-implementation, prs-review, discussions-review) all exist in assets/, are exactly one level deep, clearly signaled by the routing section, and explicitly loaded just-in-time — good structure. The main gap is the ~35-entry Lessons-learned log inlined in SKILL.md, which is reference material that belongs in a separate file; this keeps it below anchor 5 but above anchor 3 since the routing/organization itself is solid.

4 / 5

Total

13

/

20

Passed

Description

36%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 names the right domain artifacts but relies on a single generic verb ('Batch processing') with an 'etc.' hedge, and entirely lacks any 'when to use' trigger guidance. It would rarely be selected with confidence over other repo-management skills. Adding explicit trigger conditions and concrete per-artifact actions would move it up two levels.

Suggestions

Add an explicit trigger clause, e.g. 'Use when asked to review or act on GitHub issues, pull requests, or discussions in an open source repository, especially in bulk.'

Replace 'Batch processing' with the concrete actions per artifact, e.g. 'Triages, reviews, and comments on open source issues, PRs, and discussions; implements accepted issues.'

Drop 'etc.' and add natural synonyms users would say (GitHub, open source, pull requests) to sharpen trigger matching and distinctiveness.

DimensionReasoningScore

Specificity

The description names domain artifacts ('issues, PRs, discussions, implementations') but the only stated action is the generic 'Batch processing', hedged with 'etc.' — matching the anchor for domain named but actions minimal or generic. It does not reach anchor 3 because no concrete action (review, analyze, implement, triage) is actually stated.

2 / 5

Completeness

There is a vague 'what' ('Batch processing issues, PRs, discussions, implementations, etc.') and no 'when' clause or equivalent trigger guidance at all, which also caps the score at 3. It fits anchor 2 (vague what, no when) rather than 3 because the 'what' itself is generic and open-ended with 'etc.'.

2 / 5

Trigger Term Quality

'issues, PRs, discussions' are natural terms a user would say, but common variations and synonyms are missing — no 'GitHub', 'open source', 'repository', 'review', or file extensions. This matches 'some relevant keywords but missing common variations'; not 4 because the coverage is sparse and 'batch processing' is jargon users would not say.

3 / 5

Distinctiveness Conflict Risk

Naming 'issues, PRs, discussions' gives it some specificity, but 'Batch processing ... etc.' would overlap with any repository- or issue-management skill and gives no distinguishing niche like 'open source'. Somewhat specific but could still overlap with similar skills — anchor 3, not 4 because the overlap surface is broad.

3 / 5

Total

10

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

griddynamics/rosetta

Path

.claude/skills/daily-oss/SKILL.md

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.