CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-monitor-pr-ci

Monitor OneKey PR checks and review threads, fix failures, address comments, and continue until the PR is ready.

64

Quality

77%

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 ./.skillshare/skills/1k-monitor-pr-ci/SKILL.md
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.

The body is a highly actionable, well-sequenced monitoring workflow with executable commands and explicit validation/feedback loops. Its main weakness is minor redundancy across the step bodies, Important Notes, and Error Handling sections.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's competence, giving concrete commands without explaining known concepts; minor redundancy between the step bodies, 'Important Notes', and 'Error Handling' keeps it just below 5.

4 / 5

Actionability

Fully executable, copy-paste-ready commands cover the common cases — `yarn agent:check --json-file`, `gh run view --log-failed`, GraphQL resolveReviewThread mutations, and `gh api ... replies` — with concrete examples for failed checks, threads, and gate blockers.

5 / 5

Workflow Clarity

Clear sequenced poll loop with explicit validation checkpoints (Step 1c decision table, fixable-vs-preexisting verification, per-iteration CLOSED/MERGED state check) and feedback loops (fix -> push -> wait 30s -> re-poll), satisfying the destructive/batch validation requirement.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections (Usage, Input, Step 0-4, Polling Rules, Important Notes, Error Handling) and appropriately self-contained with no bundle files; minor organization gaps from duplicated guidance keep it from 5.

4 / 5

Total

18

/

20

Passed

Description

66%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 clearly communicates what the skill does with several concrete actions, but it omits any explicit 'when to use' trigger guidance, which the rubric caps at completeness 3. Trigger terms are good but lack common synonyms like 'CI' and 'pull request'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to monitor a OneKey pull request's CI checks and review comments with polling and automatic fixes.'

Include common synonyms such as 'CI', 'pull request', and 'reviews' to broaden natural trigger coverage.

Specify the kinds of failures handled (lint, types, tests) to lift specificity from 4 toward 5.

DimensionReasoningScore

Specificity

Names the domain ('OneKey PR checks and review threads') and several concrete actions ('Monitor', 'fix failures', 'address comments', 'continue until the PR is ready'); falls short of 5 because the actions remain somewhat generic without enumerating which kinds of failures or comments.

4 / 5

Completeness

Clearly answers 'what' but provides no explicit 'Use when...' trigger clause; per the rubric a missing explicit trigger guidance caps completeness at 3 even though the 'what' is clear.

3 / 5

Trigger Term Quality

Includes natural phrases a user would say ('PR checks', 'review threads', 'fix failures', 'address comments'); not 5 because common synonyms like 'CI', 'pull request', and 'reviews' are absent.

4 / 5

Distinctiveness Conflict Risk

The 'OneKey PR' niche and the 'monitor/continue until ready' framing make it mostly distinct; minor overlap risk remains with general PR-review or CI-monitoring skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
OneKeyHQ/app-monorepo
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.