CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-create-pr

Creates a Pull Request from current changes for OneKey app-monorepo. Use when user wants to create PR, submit changes, or merge feature branch. Handles branch creation, commit, push, and PR creation with conversation context extraction for code review AI.

67

Quality

80%

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-create-pr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 highly actionable with executable commands and a complete PR template, and is well-structured for a self-contained skill. Conciseness is dragged down by restated context-extraction guidance, and workflow clarity is capped at 3 because destructive/batch steps (git add ., push, auto-merge) lack explicit validation checkpoints.

Suggestions

Add validation checkpoints before destructive steps: verify git status/clean tree before 'git add .', confirm the pushed branch exists and CI is green before 'gh pr merge --auto --squash'.

Trim the 7-item context-extraction guideline list to the non-obvious items only (issue ID handling, platform impact); Claude already knows to capture intent, root cause, and design decisions.

Tighten branch-name generation by giving a concrete command or naming regex instead of only describing the feat/fix/refactor/chore prefixes.

DimensionReasoningScore

Conciseness

Mostly efficient with clear sections and code blocks, but the 7-item context-extraction guideline list restates intent/root cause/design decisions Claude already knows, adding padding that could be tightened.

3 / 5

Actionability

Provides copy-paste-ready commands (gh pr create, yarn agent:check, base-branch bash snippet) and a full PR body template covering the common case end-to-end.

5 / 5

Workflow Clarity

The 11-step sequence is well ordered, but destructive/batch operations (git add ., git push, gh pr merge --auto --squash, gh pr update-branch) lack validation checkpoints between commit and push, which caps this score at 3 per the rubric.

3 / 5

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-organized with clearly labeled sections, and the inline PR template and base-detection snippet are appropriately placed for a single-task skill.

5 / 5

Total

16

/

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 cleanly answers both what and when with a concrete trigger clause and a distinct OneKey-specific niche. Specificity and trigger-term coverage are strong but could enumerate a few more actions and synonyms.

DimensionReasoningScore

Specificity

Quotes 'Creates a Pull Request from current changes' and 'Handles branch creation, commit, push, and PR creation with conversation context extraction' list several concrete actions; not a 5 because the merge/update-branch/auto-merge steps from the body are not enumerated here.

4 / 5

Completeness

Clearly states what ('Creates a Pull Request... Handles branch creation, commit, push, and PR creation') and gives an explicit 'Use when user wants to create PR, submit changes, or merge feature branch' trigger clause.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say — 'create PR', 'submit changes', 'merge feature branch'; not a 5 because common synonyms like 'open a pull request' or 'review my changes' are absent.

4 / 5

Distinctiveness Conflict Risk

The 'OneKey app-monorepo' niche plus PR-creation triggers form a clear, narrowly scoped niche with minimal overlap risk against other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.