CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-patch-package-workflow

Create or regenerate patch-package patches, including resolutions failures and build-artifact verification.

68

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 tight, fully executable workflow with explicit validation and recovery steps, well-organized for a single-purpose skill that needs no external references.

DimensionReasoningScore

Conciseness

The body is lean: it states where patches live and the rule against hand-editing, then jumps straight to executable commands with terse inline notes like '# npx, not yarn'. It assumes Claude's competence and adds no concept padding, matching the top anchor.

3 / 3

Actionability

Every section provides complete, copy-paste-ready bash (generate, fallback via Yarn cache diff, and verify commands) with concrete file paths and flags, matching the fully-executable top anchor.

3 / 3

Workflow Clarity

The process is clearly sequenced (Generate -> Fallback -> Verify (required)) with explicit validation checkpoints ('git apply --check ... must pass', 'grep -c ... must be 0') and a recovery loop ('else rm -rf ... regenerate'), matching the top anchor.

3 / 3

Progressive Disclosure

At under 50 lines with no external references needed, the content is well-organized into clear sections (Generate, Fallback, Verify); per the simple-skills scoring note this qualifies for the top anchor without bundle files.

3 / 3

Total

12

/

12

Passed

Description

67%

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 specific and distinctive about the patch-package workflow, but omits any explicit 'when to use' trigger guidance, which limits its completeness and trigger-term coverage.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when creating or regenerating patch-package patches, or when patch generation fails with resolutions errors.'

Broaden trigger terms with natural phrasings users would say, such as 'patch not applying', 'regenerate a patch', or 'patch-package failure'.

DimensionReasoningScore

Specificity

Names the concrete tool and multiple specific actions: 'Create or regenerate patch-package patches, including resolutions failures and build-artifact verification.' It lists several concrete operations rather than vague language, matching the top anchor.

3 / 3

Completeness

It clearly answers 'what' (create/regenerate patches, handle failures, verify artifacts) but provides no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

'patch-package patches' is a relevant natural term, but coverage is thin and lacks common variations or scenario-based phrasing; it stops short of the broad natural-term coverage of the top anchor.

2 / 3

Distinctiveness Conflict Risk

The patch-package niche with resolutions/build-artifact specifics is a clear, distinct trigger set unlikely to fire for unrelated skills, matching the top anchor.

3 / 3

Total

10

/

12

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

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.