CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-patch-package-workflow

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

63

Quality

75%

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 ./.skillshare/skills/1k-patch-package-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 content is an exemplary lean, actionable skill: executable commands, explicit validation with feedback loops, and clean section structure without any padding or redundant explanation.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it states where patches live, the never-hand-edit rule, and jumps straight into executable steps with no concept explanation or padding.

5 / 5

Actionability

Concrete, mostly copy-paste-ready bash commands are provided for generate, fallback, and verify; templated placeholders like <pkg>, <version>, and <rel/path/File.ext> are minor gaps requiring substitution.

4 / 5

Workflow Clarity

A clear Generate → Fallback → Verify sequence includes explicit validation checkpoints (git apply --check must pass; grep android/build must be 0) and a feedback loop (rm -rf build dir and regenerate), satisfying destructive-operation requirements.

5 / 5

Progressive Disclosure

Under 50 lines, single-purpose, with no external references needed and three well-organized sections; per the guideline this qualifies for a top score on well-organized structure alone.

5 / 5

Total

19

/

20

Passed

Description

58%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 specific and distinctive, naming a clear niche and several concrete capabilities, but it omits any explicit trigger guidance, which limits completeness and natural trigger-term coverage.

Suggestions

Append a "Use when..." clause naming natural triggers, e.g. "Use when creating or fixing patch-package patches, resolving 'Couldn't find any versions' errors, or verifying build artifacts."

Add common synonyms/variations users might say, such as "yarn patch", "patch-file", or "node_modules patch", to broaden trigger-term coverage.

Clarify the trigger context (e.g. OneKey/yarn-resolutions workflows) so it is more distinguishable from generic npm patching skills.

DimensionReasoningScore

Specificity

"Create or regenerate patch-package patches, including resolutions failures and build-artifact verification" names the domain plus several concrete actions (create, regenerate, handle resolution failures, verify build artifacts), with only minor coverage gaps.

4 / 5

Completeness

The "what" is clear (create/regenerate patches with failure handling and verification), but there is no "Use when..." trigger clause, capping completeness at 3 per the guideline.

3 / 5

Trigger Term Quality

Relevant terms like "patch-package" and "patches" appear, but they lean technical and lack common variations or synonyms a user might naturally say.

3 / 5

Distinctiveness Conflict Risk

"patch-package patches" carves a clear, specific niche unlikely to conflict with unrelated skills, with only minor overlap risk against adjacent yarn/npm tooling skills.

4 / 5

Total

14

/

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

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.