search-repos
Skill4 starsChanged 7 months agoMITView on GitHub
Search for open source repositories on Gitee with advanced filtering by language, popularity, and activity. Use when the user wants to find repositories, explore open source projects, discover libraries by language, or compare multiple projects without forking. Keywords: search repos, find repositories, open source discovery, explore projects, compare libraries.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- matthewmturner/skillstheir own version, first seen Jul 14, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- matthewmturner/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- close-issue-flowSkill
- create-issueSkill
- create-prSkill
- create-releaseSkill
- daily-digestSkill
- implement-issueSkill
- merge-pr-checkSkill
- quick-fix-suggestionSkill
- repo-explorerSkill
- review-prSkill
- search-and-forkSkill
- stale-pr-reminderSkill
- triage-issuesSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Search for open source repositories with advanced filters.
- Very specific: line 24
Use search-repos when the user wants to:
- Very specific: line 62
Call search_open_source_repositories with parameters:
- Distinctive: line 117
Ask which repository (by number or name)
- Very specific: line 118
Check if repo-explorer skill is available
- Distinctive: line 119
If yes: "I'll use the repo-explorer skill to analyze [owner/repo]"
- Very specific: line 120
If no: Use get_file_content to manually read README and key files
- Distinctive: line 124
If results are unsatisfactory, adjust:
- Distinctive: line 181
Consider both English and Chinese keywords for broader coverage
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Search Repositories on Gitee
Search for open source repositories with advanced filters. After finding interesting projects, optionally explore them in depth.
Prerequisites
- Gitee MCP Server configured
- Required tool:
search_open_source_repositories - Optional:
repo-explorerskill for deep dives
When to Use This Skill
Use search-repos when the user wants to:
- Find repositories by language (Go, Python, Java, etc.)
- Discover projects by keywords or categories
- Compare multiple repositories
- Explore without immediate forking intent
Not for: Forking repositories (use search-and-fork instead)
Supported Filters
| Parameter | Type | Description | Example |
q | string | Required. Search keywords | "web framework", "ORM" |
language | string | Filter by programming language | "Go", "Python", "JavaScript" |
sort | string | Sort field: stars_count, forks_count, watches_count, created_at, last_push_at | stars_count |
order | string | Sort direction: desc (default), asc | desc |
owner | string | Filter by namespace/organization | "oschina", "alibaba" |
fork | boolean | Include forked repositories | false (default) |
Workflow
Step 1: Gather Requirements
Ask the user:
- Keywords - What functionality? (e.g., "web framework", "database ORM")
- Language - Programming language preference? (Go / Python / Java / JavaScript / TypeScript / Rust / etc.)
- Sort by - Popularity (
stars_count) or recent activity (last_push_at)? - Filters - Include forks? Specific organization?
Step 2: Build Search Queries
Try multiple keyword variations for better coverage:
- English: "web framework"
- Chinese: "web 框架"
- Related terms: "HTTP router", "REST API framework"
Step 3: Execute Search
Call search_open_source_repositories with parameters:
{
q: "web framework",
language: "Go", // If specified
sort: "stars_count", // or "last_push_at"
order: "desc",
per_page: 20
}Step 4: Present Results
Format output as:
## 🔍 Search Results: [keywords] ([language])
Found N repositories (sorted by [criteria]):
| # | Repository | ⭐ Stars | 🍴 Forks | Language | Updated |
|---|------------|---------|----------|----------|---------|
| 1 | owner/repo | 1.2k | 150 | Go | 2 days ago |
| 2 | owner/repo | 890 | 98 | Go | 1 week ago |
| 3 | owner/repo | 650 | 75 | Go | 3 weeks ago |
---
### 📋 Detailed Information
**#1: [Full Repository Name]**
- **URL**: https://gitee.com/owner/repo
- **Description**: [Full description from API]
- **License**: [license type if available]
- **Tags**: [topics if available]
**#2: [Full Repository Name]**
[Same format...]Step 5: Offer Next Actions
After presenting results:
What would you like to do next?
1. 🔍 **Refine search** - Try different keywords/filters
2. 🔎 **Deep dive** - Explore a specific repository (requires repo-explorer skill)
3. 📊 **Compare** - View side-by-side comparison
4. ✅ **Done** - End the sessionIf user chooses "Deep dive":
- Ask which repository (by number or name)
- Check if
repo-explorerskill is available - If yes: "I'll use the repo-explorer skill to analyze [owner/repo]"
- If no: Use
get_file_contentto manually read README and key files
Step 6: Iterative Refinement
If results are unsatisfactory, adjust:
- Broader or more specific keywords
- Different language filter
- Change sort criteria
- Toggle fork inclusion
Example Conversations
Example 1: Language-specific search
User: Find me Python machine learning libraries
→ search_open_source_repositories(
q="machine learning",
language="Python",
sort="stars_count"
)Example 2: Active projects
User: Show me recently updated Go web frameworks
→ search_open_source_repositories(
q="web framework",
language="Go",
sort="last_push_at"
)Example 3: Discovery without specific goal
User: What are popular JavaScript UI libraries?
→ search_open_source_repositories(
q="UI component",
language="JavaScript",
sort="stars_count"
)
→ User: Can you explore the first one?
→ Check for repo-explorer skill and use itComparison with Related Skills
| Task | Use This | Instead Of |
| Search without fork intent | search-repos ✅ | search-and-fork |
| Search + Fork in one flow | search-and-fork ✅ | search-repos |
| Deep exploration after search | Both can lead to repo-explorer | - |
Notes
- Results limited to public repositories on Gitee
- Language names use GitHub conventions (e.g., "Go", not "Golang")
- Keyword variations yield different results - experiment with synonyms
- Consider both English and Chinese keywords for broader coverage
- The
repo-explorerskill provides detailed analysis; this skill focuses on discovery
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

