CtrlK
BlogDocsLog inGet started
Tessl Logo

gh-bulk-issues

Orchestrate parallel Mastra Code headless instances to debug and fix multiple GitHub issues simultaneously

56

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.mastracode/skills/gh-bulk-issues/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, actionable playbook with clear sequencing and validation for a batch operation. Resolving the mastracode path placeholder and tightening the redundant intro would push conciseness and actionability to 5.

DimensionReasoningScore

Conciseness

Largely lean imperative directives and command blocks with minimal conceptual padding; the opening paragraph partly restates the description and a few explanatory clauses could be trimmed.

4 / 5

Actionability

Provides concrete executable commands (git worktree, pnpm build, mc invocation, gh pr checks) with clear parameterization; minor gaps like the unresolved '<path-to-mastracode>' placeholder keep it from a 5.

4 / 5

Workflow Clarity

Clear sequenced workflow (setup, monitoring, finish, PR review, CI) with validation checkpoints and feedback loops (restart timed-out instances with context, re-check CI) for a batch operation; a few checkpoints like verifying build success before spawning mc are only implicit.

4 / 5

Progressive Disclosure

Single self-contained SKILL.md with well-organized section headers (Inputs, Setup, Monitoring, etc.) and no nested references; at ~90 lines it slightly exceeds the simple-skill threshold that would allow a 5.

4 / 5

Total

16

/

20

Passed

Description

53%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 concrete and distinct but stops at stating what the skill does without any 'when to use it' trigger guidance, which caps several dimensions. Adding a 'Use when...' clause and broader trigger synonyms would lift completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user wants to fix multiple GitHub issues in parallel or asks to bulk-process a list of issue numbers.'

Broaden trigger terms with natural synonyms users say: 'bugs', 'tickets', 'issue list', 'bulk fix'.

Expand the action list to preview the supervision steps (spawn workers, monitor, review diffs, open PRs) for fuller specificity.

DimensionReasoningScore

Specificity

Names the domain ('Orchestrate parallel Mastra Code headless instances') and two concrete actions ('debug and fix'), but does not enumerate the orchestration actions (spawn, monitor, review, PR) that the body covers.

3 / 5

Completeness

Clearly states what the skill does, but provides no 'Use when...' trigger clause; per the rubric a missing explicit trigger guidance caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant keywords ('GitHub issues', 'debug', 'fix') but lacks common variations or synonyms a user might say ('bugs', 'tickets', 'issue list', 'bulk').

3 / 5

Distinctiveness Conflict Risk

Targets a clear niche (parallel headless orchestration of multiple GitHub issues) with minimal overlap risk versus single-issue or generic PR skills.

4 / 5

Total

13

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
mastra-ai/mastra
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.