CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

weekly-plan

Use when the weekly scheduled run asks for this repository's weekly plan. Reads the past week's merged pull requests and the open issues, then posts one short plan comment on the pinned "Weekly plan" issue.

69

Quality

87%

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

88%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 procedural skill: copy-paste-ready commands, an explicit idempotency guard against double posting, and clear termination conditions. The only trims available are small redundancies between sections; no significant reorganization is needed.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — no explanation of gh, git, or CI concepts — but contains minor repetition that could be trimmed: "Never add any label to it" is restated in the Never section, and the one-plan-per-week rule appears both in its own section and in Never. This matches 'efficient; minor instances of over-explanation' rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Fully executable throughout: exact gh commands with complete --json field lists, a GraphQL query for pinned issues, a jq comment check, a literal comment template, and a deterministic field-to-status mapping (isDraft, statusCheckRollup conclusions, reviewDecision values). Nothing is pseudocode or vague.

5 / 5

Workflow Clarity

The sequence (read → find/create plan issue → check for this week's marker → post → stop) is explicit, with real validation checkpoints: the week-marker idempotency check before posting, truncation disclosure when a list hits its limit, fallback branches for zero or duplicate plan issues, and a defined stop condition covering gh failure. These are explicit validation steps with error handling, matching anchor 5.

5 / 5

Progressive Disclosure

Sections are well-organized with clear headers and no orphaned references (no bundle files exist, and the body references none), so navigation is easy. However, at roughly 105 lines — above the under-50-line simple-skill exception — inline material like the comment template and status-mapping rules could arguably live in a reference file, matching 'good structure; minor organization gaps' rather than anchor 5.

4 / 5

Total

18

/

20

Passed

Description

80%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 with explicit 'Use when...' trigger guidance, third-person voice, and concrete actions. Its only weakness is narrow trigger vocabulary — it covers 'weekly plan' well but includes no natural synonyms a user might say instead.

DimensionReasoningScore

Specificity

"Reads the past week's merged pull requests and the open issues" and "posts one short plan comment on the pinned 'Weekly plan' issue" name several concrete actions on a specific artifact. Minor gaps in coverage (CI failures and plan-issue creation are handled in the body but not mentioned) keep it below the comprehensive anchor 5.

4 / 5

Completeness

It explicitly answers both questions: "Use when the weekly scheduled run asks for this repository's weekly plan" gives a concrete when, and "Reads... then posts one short plan comment" gives a clear what. The when is already specific, so anchor 4's 'could be more explicit' does not apply.

5 / 5

Trigger Term Quality

"weekly scheduled run" and "weekly plan" are natural phrases for this niche, but the trigger vocabulary is narrow — no synonyms or variations such as "weekly report", "weekly summary", or "handoff". This matches 'some relevant keywords but missing common variations' rather than the good-coverage anchor 4.

3 / 5

Distinctiveness Conflict Risk

The repository-scoped weekly-planning niche, the pinned "Weekly plan" issue, and the scheduled-run trigger make this clearly distinguishable from any other skill with minimal conflict risk.

5 / 5

Total

17

/

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

chandler767/WorkJournal

Path

tessl-factory/skills/weekly-plan/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.