CtrlK
BlogDocsLog inGet started
Tessl Logo

rebase-conflict

Resolve merge conflicts between a pull request and production changes in the cloudflare-docs repository.

58

Quality

66%

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 ./.flue/.agents/skills/rebase-conflict/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 a well-structured, lean, instruction-only workflow with concrete tool guidance and an explicit confidence gate. It scores consistently at 4, held from 5 only by the lack of an error-recovery feedback loop and mild redundancy.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence (no explaining what merge conflicts or MDX are), and every section is operational; the only minor trim is mild redundancy between process step 4/5 and the output-schema notes on the confidence gating.

4 / 5

Actionability

It names specific tools (get_commit_pr, read_repo_file), the three SHA refs to use with them, file entry fields, and an exact JSON output schema — concrete and actionable for an instruction-only skill, with only the exact tool call signatures left implicit.

4 / 5

Workflow Clarity

A clear five-step sequence with an explicit confidence quality-gate (high/medium/low controlling whether files are returned) serves as the checkpoint, but there is no validate->fix->retry feedback loop, which would be needed for a 5.

4 / 5

Progressive Disclosure

A single self-contained file with no external bundles and well-organized sections (Inputs, Process, Security, Output schema, Tool usage); at ~75 lines it slightly exceeds the 50-line simple-skill threshold, so it lands just below the 5 reserved for clearly split, navigable content.

4 / 5

Total

16

/

20

Passed

Description

57%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 highly distinct, but it omits an explicit "Use when..." trigger clause and only lists a single action, which caps both completeness and specificity at the midpoint. It is solid but lacks the explicit usage trigger that would lift it above average.

Suggestions

Add an explicit 'Use when...' clause naming the trigger, e.g. 'Use when rebasing a pull request onto production and conflicts arise.'

Enumerate the concrete actions involved (e.g. inspecting conflict files, merging PR and production intent, emitting resolved MDX) to broaden specificity beyond the single 'resolve' verb.

Include natural trigger synonyms users might say (e.g. 'rebase conflicts', 'conflict markers') to improve keyword coverage.

DimensionReasoningScore

Specificity

Names a concrete action ("Resolve merge conflicts"), the domain ("cloudflare-docs repository"), and operands ("pull request and production changes"), but lists only one action rather than a comprehensive set, matching the anchor that names the domain with 1-2 concrete actions.

3 / 5

Completeness

It clearly states what the skill does but provides no "Use when..." clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the judging guidelines; the "when" is only weakly implied by the conflict scenario.

3 / 5

Trigger Term Quality

"merge conflicts", "pull request", and "production changes" are natural terms a user would say, but there are no synonyms or common variations (e.g. "rebase", "conflict markers"), fitting the anchor for some relevant keywords missing variations.

3 / 5

Distinctiveness Conflict Risk

The description is pinned to a specific repository and a narrow rebase-conflict scenario, giving it a clear niche with distinct triggers and minimal risk of firing for an unrelated skill.

5 / 5

Total

14

/

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
cloudflare/cloudflare-docs
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.