CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

takeover

Take over a public (every-app/open-seo) PR, or a branch or agent thread, and finish it in the private repo while keeping the original contributors' credit in the merged commit. Use when the user asks to take over, finish, adopt, or land someone else's PR, or when triage decides a contributor's PR should ship.

Quality

96%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 a lean, well-sequenced takeover workflow with concrete, executable git and gh commands and exact output formats for PR descriptions and closing comments. Validation checkpoints are explicit at every risky step — reproduce the need, check main, verify the real failure with tests, and gate all merges/closures on the maintainer's go. At 46 well-organized lines requiring no bundle files, it scores top marks across all dimensions.

DimensionReasoningScore

Conciseness

Every line carries non-obvious, repo-specific instruction (the every-app/open-seo fork workflow, the noreply-address construction, the squash-merge credit behavior) with zero padding or explanation of concepts Claude already knows. Lean and efficient; every token earns its place — anchor 5, not 4, since not even minor trimming opportunities remain.

5 / 5

Actionability

The body provides copy-paste-ready commands for each phase: "git fetch https://github.com/every-app/open-seo.git pull/<n>/head", "id=$(gh api users/<login> --jq .id)", "git log origin/main -S<symbol>", "pnpm ci:check" and "pnpm test", plus exact PR-description and comment formats. The common cases are fully covered with executable commands; the only templates (the Co-authored-by trailer) are deliberately parameterized with an explicit warning against guessed emails, so this fits anchor 5 rather than 4.

5 / 5

Workflow Clarity

The five sections (Read it → Bring it in → Finish it → Close the loop → Report) give a clear sequence with explicit validation checkpoints and feedback loops: "Reproduce the bug or confirm the need yourself. If the user problem isn't real, stop and say so", "Check whether main already fixed it", "verify the real failure (not just green mocks)", and the maintainer-go gate before any merge or public-PR action. Anchor 5; validation is present at every risky juncture, so the missing-validation cap does not apply.

5 / 5

Progressive Disclosure

The skill is 46 lines with no bundle files (references/, scripts/, assets/ absent) and no need for external reference files; its only pointers are to repo documentation (docs/maintainers/preview-deployments.md) and the sibling merge-ready skill, which is a one-level-deep, clearly signaled pattern. Per the simple-skill exception, well-organized sections alone earn anchor 5 here.

5 / 5

Total

20

/

20

Passed

Description

95%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 clearly states what the skill does and gives an explicit 'Use when' clause with natural synonyms (take over, finish, adopt, land) plus a triage trigger. It occupies a distinct, low-conflict niche. Only the omission of the close-the-loop/report outcomes keeps specificity from full marks.

DimensionReasoningScore

Specificity

"Take over a public (every-app/open-seo) PR, or a branch or agent thread, and finish it in the private repo while keeping the original contributors' credit in the merged commit" lists three concrete actions with named scope. It matches anchor 4 rather than 5 because the close-the-loop and report steps from the body are absent, leaving a minor gap in coverage.

4 / 5

Completeness

The description explicitly answers both questions: the what ("finish it in the private repo while keeping the original contributors' credit in the merged commit") and the when, with concrete trigger phrases in the "Use when" clause. Clearly anchor 5; anchor 4 would require a weaker or less explicit 'when', which is not the case.

5 / 5

Trigger Term Quality

"Use when the user asks to take over, finish, adopt, or land someone else's PR, or when triage decides a contributor's PR should ship" covers four natural verb synonyms plus the triage phrasing a maintainer would use. This is comprehensive synonym coverage for the domain; file extensions do not apply, so anchor 5 fits better than 4.

5 / 5

Distinctiveness Conflict Risk

The niche is highly specific — taking over every-app/open-seo public PRs into a private repo with credit preservation — and the triggers ("take over", "land someone else's PR") are unlikely to fire for any other skill. Clear niche with distinct triggers; minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

every-app/open-seo

Path

.agents/skills/takeover/SKILL.md

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.