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.

72

Quality

88%

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

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced PR workflow with real commands and validation checkpoints, but it is monolithic and carries redundancy between the Quick Reference table, the detailed steps, and Important Notes.

Suggestions

Remove the Quick Reference table or the per-step detail to eliminate the duplicated 11-step listing; keep one canonical sequenced view to improve conciseness.

Move the PR body template and the context-extraction guidelines into a referenced file (e.g. references/pr-template.md) and link to it, so the main body stays a lean overview and progressive disclosure improves.

Trim Important Notes to only items not already stated in the workflow steps to avoid restating base-branch detection, commit format, and issue-ID handling.

DimensionReasoningScore

Conciseness

Mostly operational with no concept padding, but the 11 steps appear twice (Quick Reference table then detailed Workflow) and Important Notes repeats base-branch/commit-format guidance already covered, so it could be tightened.

2 / 3

Actionability

Provides copy-paste-ready commands throughout — git status/branch, an executable base-branch auto-detection script, yarn agent:check, git add/commit/push, and gh pr create/update-branch/merge with real flags — plus a concrete PR body template.

3 / 3

Workflow Clarity

An 11-step numbered sequence with an explicit validate→fix checkpoint ('Fix any reported lint or type errors before committing') and a post-push readiness check, covering error recovery for the semi-irreversible push/merge operations.

3 / 3

Progressive Disclosure

Well-organized into clear sections with a Quick Reference overview, but it is a single ~200-line monolithic file with no external references; the PR body template and context-extraction guidelines are inline content that could be split out.

2 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states concrete capabilities and provides explicit 'Use when' triggers scoped to a specific repository, minimizing conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'branch creation, commit, push, and PR creation with conversation context extraction' — rather than vague language.

3 / 3

Completeness

Explicitly states what it does ('Creates a Pull Request... Handles branch creation, commit, push, and PR creation') and when to use it ('Use when user wants to create PR, submit changes, or merge feature branch').

3 / 3

Trigger Term Quality

Natural user phrasings are present: 'create PR', 'submit changes', 'merge feature branch', giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Scoped to 'OneKey app-monorepo' with triggers tied to that repo's PR workflow, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.