CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-create

Use when explicitly creating or updating a Basic Memory pull request. This compatibility entry point delegates the full workflow to pull-request and the latest-head Codex gate to pr-review-loop.

69

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%Weight 40%Scale 1-3

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 lean, well-structured orchestration skill: it sequences a multi-step PR workflow with explicit validation and a Codex/CI feedback loop, keeps deprecation guidance in its own section, and gives concrete actionable instructions throughout.

DimensionReasoningScore

Conciseness

The ~40-line body assumes Claude's knowledge (no explanation of what a PR or CI is) and confines deprecation detail to a dedicated "Compatibility" section, so every token earns its place per the score-3 anchor.

3 / 3

Actionability

Specific, actionable instructions dominate: "Confirm commits are signed off", "title follows the repository's semantic PR-title format", "Do not enable auto-merge", and named tools (`pull-request`, `pr-description`, `fix-pr-issues`); per the scoring notes, instruction-only skills are not penalized for lacking code when guidance is this concrete.

3 / 3

Workflow Clarity

Six numbered steps give a clear sequence, step 3 is an explicit validation checkpoint, and step 6 defines a feedback loop ("If Codex or CI reports a blocker, use `fix-pr-issues`, push the fix, and restart `pr-review-loop`"), matching the score-3 anchor of clear sequence with validation and error recovery.

3 / 3

Progressive Disclosure

Under 50 lines with no bundle references needed (only assets/icon.svg exists), the content is organized into clearly signaled Compatibility/Workflow/Report sections and points one level deep to peer skills, meeting the score-3 simple-skill allowance for well-organized sections.

3 / 3

Total

12

/

12

Passed

Description

67%Weight 40%Scale 1-3

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 has an explicit trigger and answers both what and when, but its capability statement is delegation metadata laced with internal jargon ("latest-head Codex gate") rather than concrete user-facing actions, and it overlaps with the pull-request skill it delegates to.

Suggestions

Lead with the concrete actions the user gets (e.g., "Open or update a Basic Memory pull request with a generated body and a Codex/CI review gate") before the delegation note.

Add the common abbreviation "PR" alongside "pull request" so natural phrasings like "create a PR" match the trigger.

Clarify how this entry point differs from invoking `pull-request` directly so it is less likely to conflict with that sibling skill.

DimensionReasoningScore

Specificity

Quotes "creating or updating a Basic Memory pull request" and "delegates the full workflow to pull-request" name a domain and a couple of actions, but the capability is framed as delegation rather than a comprehensive list of concrete actions, matching the score-2 anchor.

2 / 3

Completeness

An explicit "Use when explicitly creating or updating a Basic Memory pull request" trigger answers when, and "This compatibility entry point delegates the full workflow to pull-request and the latest-head Codex gate to pr-review-loop" answers what, satisfying the score-3 anchor of clearly answering both with explicit triggers.

3 / 3

Trigger Term Quality

Natural terms like "creating", "updating", "pull request", and "Basic Memory" appear, but common variations such as "PR" are absent, fitting the score-2 anchor of some relevant keywords missing common variations.

2 / 3

Distinctiveness Conflict Risk

The "Basic Memory pull request" niche and "compatibility entry point" framing are specific, but it deliberately delegates to a sibling `pull-request` skill, creating real overlap risk, matching the score-2 anchor of somewhat specific but still overlapping similar skills.

2 / 3

Total

9

/

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
basicmachines-co/basic-memory
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.