How do I install the Find Repos skill?

Run npx skillmds@latest add furkankoykiran/find-repos in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Find Repos safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Find Repos?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Find Repos free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Find Repos?

furkankoykiran (@furkankoykiran) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Find Repos by furkankoykiran — Agent Skill

Name: Find Repos
Author: furkankoykiran

File contents

Find repositories in $ORGANIZATION organization with open issues that match your profile.

Your Profile (from config.json)

Profile information is read from ~/.claude/config.json:

Website: From profiles.website
Blog: From profiles.blog
GitHub: From profiles.github

Discovering My Interests (Do this first!)

Before searching for issues, dynamically discover my current interests:

Use GitHub MCP to fetch my repositories and starred repos
Read my website (from config.json profiles.website) to understand my focus
Analyze my blog (from config.json profiles.blog) for recent topics
Look for patterns in languages, frameworks, and domains
Infer interests dynamically - don't use static assumptions

GitHub Tools

GitHub MCP: Preferred for collaboration (PRs, issues, comments, reviews). Tool names follow mcp__github__*.
gh CLI: Fallback when MCP unavailable - gh --help for commands

Search Steps

Search Repositories: Using GitHub MCP, search for repositories in $ORGANIZATION that:
- Are actively maintained
- Have open issues
- Use languages/technologies aligned with your interests (check your profile)
Filter Issues: From these repos, identify at most one most suitable issue per repository. Apply strict filters:
- ✅ Open state
- ✅ No linked or referencing PRs (verify via linked PRs section or PR search)
- ✅ Created or updated within last 6 months
- ✅ Has labels: good first issue, help wanted, bug, documentation, or enhancement
- ✅ Not assigned to anyone
- ✅ Tech stack aligns with your interests (Python, TypeScript, MCP, AI/LLM, Telegram, etc.)
Compile Results: For final selected issues (one per repo, max 5-7), create a table with:
- Repository Name (URL)
- Issue Number & Title (direct link)
- Brief task summary
- Difficulty Level (Easy/Medium/Hard)
- Primary Languages/Technologies
- Date of Last Update
- No Open PR confirmation ("✅ Verified, no linked PR")
- Why This Fits Your Profile: Short relevance explanation
Present: Show the list clearly, highlight top 3 with reasoning, and await approval to contribute.

Usage

/find-repos ORGANIZATION=microsoft

---name: find-reposdescription: Find contribution opportunities across an entire GitHub organisation, ranked by fit against the profile in ~/.claude/config.json. Use when no single repo is named.---Find repositories in `$ORGANIZATION` organization with open issues that match your profile.## Your Profile (from config.json)Profile information is read from `~/.claude/config.json`:- **Website**: From `profiles.website`- **Blog**: From `profiles.blog`- **GitHub**: From `profiles.github`## Discovering My Interests (Do this first!)Before searching for issues, dynamically discover my current interests:1. Use GitHub MCP to fetch my repositories and starred repos2. Read my website (from `config.json` profiles.website) to understand my focus3. Analyze my blog (from `config.json` profiles.blog) for recent topics4. Look for patterns in languages, frameworks, and domains5. Infer interests dynamically - don't use static assumptions## GitHub Tools- **GitHub MCP**: Preferred for collaboration (PRs, issues, comments, reviews). Tool names follow `mcp__github__*`.- **gh CLI**: Fallback when MCP unavailable - `gh --help` for commands## Search Steps1. **Search Repositories**: Using GitHub MCP, search for repositories in `$ORGANIZATION` that: - Are actively maintained - Have open issues - Use languages/technologies aligned with your interests (check your profile)2. **Filter Issues**: From these repos, identify **at most one** most suitable issue per repository. Apply strict filters: - ✅ Open state - ✅ No linked or referencing PRs (verify via linked PRs section or PR search) - ✅ Created or updated within last 6 months - ✅ Has labels: `good first issue`, `help wanted`, `bug`, `documentation`, or `enhancement` - ✅ Not assigned to anyone - ✅ Tech stack aligns with your interests (Python, TypeScript, MCP, AI/LLM, Telegram, etc.)3. **Compile Results**: For final selected issues (one per repo, max 5-7), create a table with: - Repository Name (URL) - Issue Number & Title (direct link) - Brief task summary - Difficulty Level (Easy/Medium/Hard) - Primary Languages/Technologies - Date of Last Update - No Open PR confirmation ("✅ Verified, no linked PR") - **Why This Fits Your Profile**: Short relevance explanation4. **Present**: Show the list clearly, highlight top 3 with reasoning, and await approval to contribute.## Usage```/find-repos ORGANIZATION=microsoft```

Frequently asked questions

Find Repos