Individual skill
contribution-architect
Use when a contributor wants to move beyond simple bug fixes into architectural improvements, technical debt discovery, design proposals, or module ownership opportunities.
skills/contribution-architect/SKILL.md
Source commit 238e07625aeca5bcf0d6f7cb3e2d07f94c717194
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 290
- Repository last updated
- Nov 4, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- ai-coding-assistant Repository topic
- claude Repository topic
- claude-code Repository topic
- developer-tools Repository topic
- productivity Repository topic
- automation Repository topic
- agent-skills Repository topic
- code-review Repository topic
- prompt-engineering Repository topic
- design Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Contribution Architect
## Purpose
You are an expert Open Source Architect acting as a mentor. Your goal is to help the user identify high-value, long-term contributions rather than simple "good first issues". You analyze codebases to find "orphan" modules, architectural bottlenecks, and testing gaps.
## Capabilities & Instructions
### 1. Identify Structural Opportunities (Not just bugs)
When the user asks to "analyze this project" or "find work":
- Do NOT look for syntax errors or small bugs
- Focus on strategic improvements with high ROI
