CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

trail-sense-sync-priority-project

Sync the Trail Sense Priorities GitHub project (kylecorry31 project 2) with the repo's open issues - remove closed and community only issues, and rank new and misplaced issues for approval before adding or moving them. Use when asked to sync with issues or update the priority project.

Quality

95%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary instruction-only skill body: dense with operational specifics, fully executable commands, and a workflow with explicit completion criteria, an approval gate, dry-run validation, and a post-apply verification pass. The ranking criteria translate subjective maintainer preferences into concrete, checkable rules.

DimensionReasoningScore

Conciseness

Every sentence carries project-specific knowledge Claude could not infer — the project URL and ID, that 'manual table order is the ranking, so there is no rank field', the 'Item closed' workflow behavior, and the tool tiers — with no padding or explanation of known concepts across ~39 lines. Re-reading anchor 4 ('minor instances of over-explanation that could be trimmed'), nothing here explains a concept Claude already knows, so anchor 5 is the better fit.

5 / 5

Actionability

Commands are copy-paste ready with full paths (`python3 .agents/skills/trail-sense-sync-priority-project/scripts/sync_plan.py`, the graphql workflows query, `gh issue view <n>`, `apply_changes.py <plan.json> --dry-run`) plus an exact JSON plan format with a worked example. The common cases (new, misplaced, no_single_priority, duplicates, removals) each get specific handling rules, matching anchor 5 rather than anchor 4's 'minor gaps'.

5 / 5

Workflow Clarity

Six sequenced steps each end with an explicit completion criterion ('This step is complete when...'), and the batch/destructive risk is covered by real validation: a user approval gate ('Do not change the project before then'), a dry-run before the real run, and a step-5 re-run that must come back clean — a full validate-apply-reverify feedback loop. The batch-operation cap at 3 does not apply since validation is explicitly present, and anchor 4's 'minor validation gaps' is not met.

5 / 5

Progressive Disclosure

At ~39 lines with no need for external prose references, the skill is well organized into overview, Workflow, and Ranking criteria sections; both scripts referenced in the body (scripts/sync_plan.py, scripts/apply_changes.py) exist in the bundle, one level deep and clearly signaled via their invocation commands. This meets the under-50-line exception for a top score.

5 / 5

Total

20

/

20

Passed

Description

87%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 strong description in third person that names the specific project and concrete actions, with an explicit 'Use when' trigger clause. Its only weaknesses are minor: it omits epic removal from the stated actions and could include a few more natural trigger variations.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'remove closed and community only issues, and rank new and misplaced issues for approval before adding or moving them' — anchored to a specific target ('kylecorry31 project 2'). It falls short of anchor 5's comprehensive coverage because the body also removes epics and surfaces no_single_priority items, which the description omits; it is clearly above anchor 3's 1-2 actions.

4 / 5

Completeness

Explicitly answers both questions: a detailed 'what' (sync the project with open issues, remove stale items, rank new/misplaced for approval) and a concrete 'when' clause with trigger phrases. This matches anchor 5 and is clearly above anchor 4, where the 'when' is present but could be more specific.

5 / 5

Trigger Term Quality

'Use when asked to sync with issues or update the priority project' supplies two natural trigger phrases a user would actually say. A few natural variations are missing ('sync the project', 'prioritize issues', 'update the project board'), which matches anchor 4's 'good keyword coverage; a few natural terms missing' rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Names the exact artifact ('the Trail Sense Priorities GitHub project (kylecorry31 project 2)'), giving it a clear niche with distinct triggers and minimal conflict risk with any other skill — a direct match for anchor 5.

5 / 5

Total

18

/

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

kylecorry31/Trail-Sense

Path

.agents/skills/trail-sense-sync-priority-project/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.