CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

coauthor-brief

Generate a co-author / collaborator handoff brief for a multi-author, multi-machine project — summarizing what changed since the last brief (git delta), the current state of each artifact (manuscript, analysis, slides), open questions, how to reproduce locally, and any restricted-data access steps. Use when user says "coauthor brief", "handoff brief", "bring my coauthor up to speed", "what changed since last week", "onboard a collaborator", "write a handoff for [name]", or before sending a co-author the repo. NOT a commit or a checkpoint — it is the cross-machine, cross-person summary `meta-governance.md` only partially covers.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/coauthor-brief/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

55%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 well-written redirect stub: admirably lean, with genuinely useful cross-agent portability rules. But as a SKILL.md it contains none of the skill's actual instructions — everything is delegated to a relative path outside the bundle that does not exist here, leaving no task workflow and no resolvable references.

Suggestions

Make the skill self-contained: inline the core procedure, or move the source instructions into a references/ file inside the skill directory, instead of pointing to `../../../.claude/skills/coauthor-brief/SKILL.md`, which only resolves in the original repo layout and breaks when the skill is synced or reviewed standalone.

Add the brief-generation workflow to the body with sequenced steps (collect git delta since last brief, assess each artifact, compile open questions, write repro and restricted-data sections) and at least one validation checkpoint, e.g. verify the delta against `git log` output before writing the summary.

Keep the cross-agent adaptation notes, but place them under an explicit heading (e.g. '## Running from another agent') and give one concrete example of $ARGUMENTS substitution so the redirect plus rules is fully actionable on its own.

DimensionReasoningScore

Conciseness

The ~25-line body is lean and imperative with zero concept explanations: it assumes competence ('Read that file now and follow it', 'Read the agent's file for what the step checks') and every bullet earns its place as a cross-agent portability rule. It matches the anchor 'lean and efficient; assumes Claude's competence; every token earns its place' rather than score 4's 'minor instances of over-explanation'.

5 / 5

Actionability

The portability rules are concrete and executable — 'Where it says `$ARGUMENTS`, use what the user asked for', 'mark every result it produced *not independently verified*', 'repeat that check in Claude Code (`/verify-claims` for citations)' — but the actual task procedure (how to generate the brief: git delta, artifact states, repro steps) is entirely absent from the body, delegated to an external file. This fits the score-3 anchor 'some concrete guidance but incomplete; missing key details' rather than score 4, whose guidance is self-sufficient.

3 / 5

Workflow Clarity

The only sequence present is a reading order ('Read [`AGENTS.md`] first if you have not already', then read the source SKILL.md); the multi-step workflow the skill exists for (gathering the git delta, per-artifact state, open questions, reproduction instructions, restricted-data steps) has no steps, checkpoints, or validation in the body. This matches anchor 2, 'rough sequence present but many gaps; steps poorly defined; validation absent', rather than anchor 3, which requires the actual task steps to be listed.

2 / 5

Progressive Disclosure

The bundle contains only SKILL.md — no references/, scripts/, or assets/ — and the sole substantive reference points outside the skill directory to `../../../.claude/skills/coauthor-brief/SKILL.md`, which does not resolve in this environment, with 'the files it points to' implying further indirection. Navigation dead-ends at a broken external path, fitting the 'minimal structure / references effectively unusable' territory of anchor 2; it is not anchor 3, whose references at least resolve and merely lack clear signaling.

2 / 5

Total

12

/

20

Passed

Description

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

An exemplary description: it states the artifact produced, itemizes its contents, lists verbatim trigger phrases including natural sentence-form requests, and explicitly disambiguates from adjacent concepts (commits, checkpoints, meta-governance.md). It is dense without padding.

DimensionReasoningScore

Specificity

The description enumerates concrete actions: 'summarizing what changed since the last brief (git delta)', 'the current state of each artifact (manuscript, analysis, slides)', 'open questions', 'how to reproduce locally', and 'any restricted-data access steps' — comprehensive coverage of the brief's sections, matching the anchor for multiple specific concrete actions rather than the score-4 anchor with minor gaps.

5 / 5

Completeness

Both halves are explicit: the 'what' is 'Generate a co-author / collaborator handoff brief ... summarizing ...' and the 'when' is a literal 'Use when user says ...' clause with concrete trigger phrases. This matches the anchor 'clearly and explicitly answers both what AND when with concrete trigger phrases'; the score-4 anchor ('when could be more explicit') does not apply since the triggers are quoted verbatim.

5 / 5

Trigger Term Quality

It quotes seven natural user phrases — "coauthor brief", "handoff brief", "bring my coauthor up to speed", "what changed since last week", "onboard a collaborator", "write a handoff for [name]", plus the situational trigger 'before sending a co-author the repo' — covering command-style invocations, synonyms, and full sentences a user would naturally say. This exceeds the score-4 anchor ('a few natural terms missing').

5 / 5

Distinctiveness Conflict Risk

The niche is precise (multi-author, multi-machine handoff briefs) and it actively disambiguates: 'NOT a commit or a checkpoint — it is the cross-machine, cross-person summary `meta-governance.md` only partially covers'. Clear niche with distinct triggers and minimal conflict risk, matching the score-5 anchor.

5 / 5

Total

20

/

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

relative_links

Relative link issues: 2 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

pedrohcgs/claude-code-my-workflow

Path

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