agentleFS
oschinaoschina/gitee-agent-skills/skills/search-repos/SKILL.md

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

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
  1. Distinctive:

    Search for open source repositories with advanced filters.

    line 14
  2. Very specific:

    Use search-repos when the user wants to:

    line 24
  3. Very specific:

    Call search_open_source_repositories with parameters:

    line 62
  4. Distinctive:

    Ask which repository (by number or name)

    line 117
  5. Very specific:

    Check if repo-explorer skill is available

    line 118
  6. Distinctive:

    If yes: "I'll use the repo-explorer skill to analyze [owner/repo]"

    line 119
  7. Very specific:

    If no: Use get_file_content to manually read README and key files

    line 120
  8. Distinctive:

    If results are unsatisfactory, adjust:

    line 124
  9. Distinctive:

    Consider both English and Chinese keywords for broader coverage

    line 181

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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-explorer skill 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

ParameterTypeDescriptionExample
qstringRequired. Search keywords"web framework", "ORM"
languagestringFilter by programming language"Go", "Python", "JavaScript"
sortstringSort field: stars_count, forks_count, watches_count, created_at, last_push_atstars_count
orderstringSort direction: desc (default), ascdesc
ownerstringFilter by namespace/organization"oschina", "alibaba"
forkbooleanInclude forked repositoriesfalse (default)

Workflow

Step 1: Gather Requirements

Ask the user:

  1. Keywords - What functionality? (e.g., "web framework", "database ORM")
  2. Language - Programming language preference? (Go / Python / Java / JavaScript / TypeScript / Rust / etc.)
  3. Sort by - Popularity (stars_count) or recent activity (last_push_at)?
  4. 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 session

If user chooses "Deep dive":

  • Ask which repository (by number or name)
  • Check if repo-explorer skill is available
  • If yes: "I'll use the repo-explorer skill to analyze [owner/repo]"
  • If no: Use get_file_content to 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 it

Comparison with Related Skills

TaskUse ThisInstead Of
Search without fork intentsearch-repos ✅search-and-fork
Search + Fork in one flowsearch-and-fork ✅search-repos
Deep exploration after searchBoth 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-explorer skill provides detailed analysis; this skill focuses on discovery

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.