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.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/pr-create/SKILL.md

Quality

Content

88%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.

This is a tight, instruction-only delegation skill: a clear sequenced workflow with validation checkpoints and an explicit error-recovery loop, a properly quarantined deprecation section, and a lean report contract. Its main weakness is that the sibling skills it depends on are referenced by bare name without any indication of where they live.

Dimension	Reasoning	Score
Conciseness	The body is lean with zero padding and assumes competence throughout; time-sensitive retired-workflow details ("BM Bossbot Approval", "bm-bossbot.yml") are correctly quarantined in a dedicated Compatibility/deprecation section. Every section earns its place, matching the 'lean and efficient' anchor.	5 / 5
Actionability	Concrete numbered steps with explicit rules ("Do not enable auto-merge", "Green CI alone is not approval") give mostly executable guidance. Minor gaps remain: delegated skills are named but not located, and steps like "confirm commits are signed off" give no command, keeping it below fully copy-paste-ready.	4 / 5
Workflow Clarity	The six-step workflow is clearly sequenced with explicit validation checkpoints (sign-off, title format, validation passed, gate on latest head SHA) and an explicit error-recovery feedback loop (blocker → `fix-pr-issues` → push → restart `pr-review-loop`). This matches the top anchor including feedback loops for error recovery.	5 / 5
Progressive Disclosure	The skill is under 50 lines with well-organized sections (Compatibility, Workflow, Report) and no inlined content that belongs in separate files. It stays at 4 rather than 5 because the one-level-deep references to sibling skills (`pull-request`, `pr-description`, `pr-review-loop`, `fix-pr-issues`) are bare names with no path or link, leaving navigation slightly ambiguous.	4 / 5
	Total	18 / 20 Passed

Description

62%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 has an explicit and well-scoped trigger clause and honestly describes its compatibility/delegation role, but it under-sells the actual capabilities and lacks natural keyword variations like "PR". It reads as a router entry rather than a full statement of what the skill accomplishes.

Suggestions

Add natural trigger variations such as "PR", "open a PR", or "submit a pull request" so users phrasing the request casually still match the skill.

Briefly enumerate the concrete outcomes (branch hygiene, signed-off commits, validated and pushed PR, Codex-gated review loop) instead of only saying the workflow is delegated.

Clarify how this entry point differs from invoking `pull-request` directly, so the description itself reduces the overlap risk with that sibling skill.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Basic Memory pull request") and one or two concrete actions ("creating or updating a pull request", "delegates the full workflow"), but does not enumerate several specific capabilities. It fits the 'names domain and 1-2 concrete actions' anchor rather than the broader coverage of a 4.	3 / 5
Completeness	Both what and when are present: "Use when explicitly creating or updating a Basic Memory pull request" is an explicit trigger, and the delegation statement says what it does. It falls short of a 5 because the 'what' is a delegation summary rather than concretely enumerated capabilities.	4 / 5
Trigger Term Quality	It includes some relevant natural keywords ("creating or updating", "pull request") but omits common variations users would say, such as "PR", "open a PR", or "submit a pull request". This matches the 'some relevant keywords but missing common variations or synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	"Basic Memory pull request" carves out a distinct niche with an explicit trigger, but the description states it delegates the full workflow to `pull-request`, creating minor overlap risk with that closely related skill. It is mostly distinct rather than a clear standalone niche.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: basicmachines-co/basic-memory
Path: .agents/skills/pr-create/SKILL.md
Commit: 194afe1

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.