CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

concurrent-agents

How to work safely when many Claude Code and Codex agents share this one checkout at once. Use before editing any file, before concluding someone reverted your work, before any branch operation, and before committing, pushing, or merging — this is almost always relevant here.

Quality

81%

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

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.

A strong, disciplined instruction-only skill: it states environment-specific rules with concrete commands, pre-action checkpoints, and if-then recovery paths for risky operations, without explaining concepts Claude already knows. The main room for improvement is trimming anecdotal justification and closing the few spots where guidance defers to another skill or stops short of a command.

Suggestions

Trim the war-story anecdotes (the overwriting incident quote and the false-revert investigation story) to one-line justifications — the rules they motivate are already clear without the narrative.

Inline the one or two essential commands deferred to other skills (e.g., the fetch command for completing shallow history, the minimal `new-branch` invocation) so the common cases are self-contained.

Consider moving "Reading a Codex peer's intent" (the Codex transcript-format walkthrough) into a reference file, keeping only the trigger conditions and the `ls` command in SKILL.md.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no git basics explained) and stays tight, but justifying anecdotes ("An agent once announced a revert from stat counts alone and was wrong; it cost a full investigation to disprove"; "Relaying between agents by hand is the user's most tedious job") and repeated "preserve and carry" phrasing are minor trim candidates. Not 5 because a few tokens are spent on narrative justification rather than instruction; not 3 because nothing is noticeably padded or over-explained.

4 / 5

Actionability

Mostly executable guidance with concrete commands ("git log --oneline <base>..HEAD", "git status --short --untracked-files=all", "git worktree list --porcelain", "gh pr list --head \"$(git branch --show-current)\" --state open") covering the common cases. Minor gaps: "fetch complete history" and "follow `new-branch`" defer to elsewhere without giving the command or essential steps inline, keeping it below the copy-paste-complete level 5.

4 / 5

Workflow Clarity

Each scenario has a clear sequence with pre-action checks and explicit if-then recovery ("If any path is unrelated or incomplete, keep the checkout in place and report the exact paths"; "If the work you were about to do just landed, continue from the latest branch snapshot"), and the revert-diagnosis section gives a decision rule (revert vs refactor hunks), so the destructive-operation validation cap does not apply. Not 5 because a couple of sections (Codex transcript reading, worktree carrying) lack explicit verification or error-recovery steps.

4 / 5

Progressive Disclosure

Good structure: clear section headers, each scenario self-contained, and clearly signaled one-level references to sibling skills in the Related section ("`new-branch` — safe branch creation...", "`ship` — the commit/push/PR workflow..."). Not 5 because the body is ~110 lines with at least one section ("Reading a Codex peer's intent") that is a distinct sub-procedure which could live in a reference file, so the under-50-line exception does not apply; not 3 because organization and signaling are genuinely good with no inline content that obviously belongs elsewhere.

4 / 5

Total

16

/

20

Passed

Description

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

A well-constructed description: it states a clear niche, explicitly covers both what it does and when to use it with multiple concrete trigger moments, and stays concise without fluff. Its only weaknesses are the abstract "work safely" framing of the capability and trigger terms that overlap generic git-workflow skills.

DimensionReasoningScore

Specificity

Names the domain ("when many Claude Code and Codex agents share this one checkout") and lists several concrete action contexts — "before editing any file", "before concluding someone reverted your work", "before any branch operation, and before committing, pushing, or merging". Not 5 because the capability itself ("How to work safely") is abstract rather than a list of concrete actions; not 3 because well more than 1-2 specific actions are enumerated.

4 / 5

Completeness

Explicitly answers both parts: the what ("How to work safely when many Claude Code and Codex agents share this one checkout at once") and the when with concrete trigger phrases ("Use before editing any file, before concluding someone reverted your work, before any branch operation, and before committing, pushing, or merging"). This matches the anchor for clearly and explicitly answering both with concrete triggers; the "almost always relevant here" note further reinforces when it applies.

5 / 5

Trigger Term Quality

Good coverage of natural terms users would say in this context: "editing", "reverted", "branch", "commit", "push", "merge", plus "agents" and "checkout". A few natural variations are missing ("stash", "rebase", "worktree", "PR"), which keeps it at 4 rather than the comprehensive synonym-level 5.

4 / 5

Distinctiveness Conflict Risk

The concurrent multi-agent shared-checkout niche is distinctive and unlikely to fire for unrelated skills, but the trigger phrases "before committing, pushing, or merging" and "before any branch operation" overlap with generic git-workflow or shipping skills. Mostly distinct with minor overlap risk against closely related skills — a 4, not the minimal-conflict 5.

4 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

BuilderIO/agent-native

Path

.agents/skills/concurrent-agents/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.