github-issues

Create, evaluate, and triage GitHub issues for CausalPy. Use when filing a bug, proposing an enhancement, analyzing existing issues, or splitting large work into parent-child sub-issues.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/github-issues/SKILL.md

Quality

Content

51%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 admirably concise and well-structured, but it delegates all actionable detail to reference files that are missing, leaving it without executable guidance, sequenced workflows, or working navigation. The strong conciseness is undermined by the absent bundle.

Suggestions

Add a brief, concrete quick-start (e.g. `gh issue create` invocation, expected body/label conventions) so the body is actionable even before consulting references.

Provide at least one sequenced workflow inline (e.g. an issue-evaluation checklist with a validation step before posting) instead of deferring entirely to reference files.

Either include the four referenced reference/*.md files in the bundle or remove the broken links so progressive disclosure navigation actually resolves.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — short overview, trigger bullets, a reference list, and a single behavioral guardrail — with no padding or re-explanation of concepts Claude already knows.	5 / 5
Actionability	Guidance is high-level ('Filing a new issue', 'Evaluating an existing issue and proposing next steps') with no concrete commands, code, label conventions, or body templates; the 'Important behavior' note is direction but not executable steps.	2 / 5
Workflow Clarity	Multi-step processes (creation, evaluation, parent-child split) are not sequenced in the body and are deferred to reference files; steps are poorly defined and validation checkpoints are absent for operations that create/modify issues.	2 / 5
Progressive Disclosure	Structure is clean and references are clearly signaled one level deep, but the referenced files (reference/issue-creation.md, bug-report.md, issue-evaluation.md, parent-child-issues.md) do not exist in the bundle, so the navigation they promise is broken.	3 / 5
	Total	12 / 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.

The description is strong: concrete, third-person, and explicitly covers both capabilities and use-when triggers with natural language. It is among the better examples, scoring at or near the top on every dimension.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Create, evaluate, and triage', 'filing a bug, proposing an enhancement, analyzing existing issues, splitting large work into parent-child sub-issues') with only minor coverage gaps, fitting the 'several specific actions' anchor rather than the comprehensive 5.	4 / 5
Completeness	Explicitly answers both what ('Create, evaluate, and triage GitHub issues for CausalPy') and when ('Use when filing a bug, proposing an enhancement, analyzing existing issues, or splitting large work into parent-child sub-issues') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('filing a bug', 'proposing an enhancement', 'analyzing existing issues', 'splitting large work') with good coverage; a few synonyms/extensions missing keeps it just below the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	Scoped narrowly to GitHub issues for CausalPy with distinct, specific triggers, giving a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 4 missing	Warning

	Total	15 / 16 Passed

Repository: pymc-labs/CausalPy
Path: .agents/skills/github-issues/SKILL.md
Commit: f94d7af

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.