author-contributions

Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.

Quality

73%

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 ./.github/skills/author-contributions/SKILL.md

Quality

Content

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

Highly actionable and well-sequenced with executable code throughout, though it carries redundant second-script content and lacks the progressive file split that a longer code-heavy skill would benefit from.

Suggestions

Consolidate or remove the 'Alternative Script' section — it duplicates step 2 logic and hard-codes a repo-specific src/vs/sessions exclusion that does not generalize.

Move the full Python script into a referenced bundle file (e.g. scripts/audit.py) and keep only the procedure and a short snippet inline to improve progressive disclosure.

Add an explicit validation checkpoint after author-identity resolution (step 1) and after classification (step 5) — e.g., 'verify the matched --author string against git log output before proceeding' — to create a feedback loop for this batch operation.

Dimension	Reasoning	Score
Conciseness	Efficient and mostly assumes competence, but the second "Alternative Script" section plus repeated notes (e.g., author matching explained twice) add length that could be trimmed.	4 / 5
Actionability	Provides fully executable bash commands and a complete, copy-paste Python script covering every procedure step; concrete examples cover the common case end to end.	5 / 5
Workflow Clarity	The seven-step procedure is clearly sequenced, but for a batch git operation the validation is implicit (exact-author-match warning) rather than an explicit verify-and-recover checkpoint, so it sits below the anchor with feedback loops.	4 / 5
Progressive Disclosure	Reasonable section structure with no bundle files present, but the example Python script and Alternative Script are inlined as a monolithic block rather than split into a referenced file; references are absent rather than signaled.	3 / 5
	Total	16 / 20 Passed

Description

81%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 strong, third-person description that clearly states the capability and concrete trigger conditions with good natural-language phrasing. Minor room to tighten coverage of output specifics.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("Identify all files a specific author contributed to", "tracing code through renames", "audit authorship before a merge") with minor coverage gaps such as not naming the table output format directly in the description.	4 / 5
Completeness	Explicitly answers both what (identify contributed files and trace renames) and when ("Use when asked who edited what... or to audit authorship before a merge") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrasing — "who edited what", "what code an author contributed", "audit authorship before a merge", and "branch vs its upstream" — covers the synonyms a user would naturally say.	5 / 5
Distinctiveness Conflict Risk	Clear niche of per-author contribution auditing across renames with distinct triggers; minimal overlap risk with other skills.	5 / 5
	Total	19 / 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: posit-dev/positron
Path: .github/skills/author-contributions/SKILL.md
Commit: 10323ef

Reviewed: 2 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.