Author Contributions
OfficialThis skill identifies and summarizes key contributors to a document or project, boosting transparency and understanding of collaborative efforts.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add microsoft/vscode --skill author-contributions -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
microsoft
Matched to the vendor's own GitHub organisation.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned microsoft/vscode at a37ac69a11.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- a37ac69a11
- Scanned
- 1 file, 169 lines
About this skill
What it does
This skill enables AI agents to retrieve and analyze contribution history directly from GitHub repositories. It allows agents to identify specific authors, track their commit patterns, and understand the evolution of codebases over time.
When to use it
- Investigating who introduced a specific bug or feature in an open-source project.
- Analyzing contributor activity to assess community health or maintainership stability.
- Verifying authorship claims before integrating third-party libraries into your workflow.
- Generating reports on code ownership for audit or compliance purposes.
Key capabilities
- Querying GitHub repositories for specific user contributions.
- Filtering results by date range, file paths, or commit types.
- Aggregating data across multiple repositories to compare author impact.
- Extracting metadata such as commit messages and associated pull requests.
Example prompts
- "Show me all commits made by 'github-actions[bot]' in the last month for the
microsoft/vscoderepository." - "List the top 5 contributors to the
reactproject based on their commit frequency over the past year." - "Find every file modified by user 'torvalds' that contains the word 'memory' in the commit message."
Tips & gotchas
Ensure your AI agent has read access to the target GitHub repositories, as private data cannot be retrieved without proper authentication. Be mindful of rate limits when querying large numbers of repositories simultaneously to avoid API throttling.