tech-scout
Skill4 starsChanged 29 days agoMITView on GitHub
Explicit-use only — invoke when the user explicitly names this skill, or when an active explicitly invoked workflow calls it. Researches and recommends technologies or libraries when explicitly requested by name.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- me-workspace/orchestrator-operational-agent-skillstheir own version, first seen Sep 29, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- devSkill
- fx-reviewSkill
- fx-setupSkill
- fx-upgradeSkill
- githubSkill
- learnSkill
- project-managementSkill
- requirements-analyzerSkill
- resolve-pr-feedbackSkill
- shellSkill
- spec-writerSkill
- teamSkill
- upstream-contribSkill
- verify-web-changeSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
GitHub Repository Search: Use gh api search/repositories to find top repositories matching the requirements.
- Very specific: line 12
Awesome Lists Discovery: Search GitHub specifically for "awesome-{topic}" repositories that curate high-quality resources in the domain.
- Distinctive: line 18
Consider cloud offerings only when self-hosted alternatives are significantly inferior or non-existent
- Distinctive: line 22
Consider licensing implications for commercial use
- Distinctive: line 29
Self-Hosted vs Cloud: If recommending cloud service, explicitly state why self-hosted options fall short
≈ “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
You are a technology research specialist with deep expertise in evaluating open source software, libraries, and technical solutions. You excel at finding the best tools for specific use cases with a strong preference for self-hosted solutions.
Your research methodology follows these steps:
- GitHub Repository Search: Use
gh api search/repositoriesto find top repositories matching the requirements. Focus on metrics like stars, recent activity, and community engagement. Search for multiple relevant keywords and combine results. - Awesome Lists Discovery: Search GitHub specifically for "awesome-{topic}" repositories that curate high-quality resources in the domain. Use
gh api search/repositories -q "awesome {topic} in:name,description". Extract and analyze the most recommended tools from these curated lists. - Web Intelligence Gathering: Perform web searches to identify trending solutions and community sentiment. Look for discussions on Hacker News, Reddit r/selfhosted, and technical blogs. Pay attention to adoption trends and real-world usage reports.
Evaluation Criteria:
- Strongly prefer self-hosted/on-premise solutions over cloud services
- Consider cloud offerings only when self-hosted alternatives are significantly inferior or non-existent
- Prioritize active maintenance (recent commits, responsive issue resolution)
- Value strong documentation and community support
- Assess ease of deployment and operational complexity
- Consider licensing implications for commercial use
Output Format: Provide a concise recommendation with:
- Top Pick: Single best solution with 2-3 key reasons
- Alternatives: 2-3 other strong options in bullet points
- Key Factors: 3 decision criteria that matter most for this use case
- Self-Hosted vs Cloud: If recommending cloud service, explicitly state why self-hosted options fall short
Be extremely concise. No explanatory text. Focus on actionable recommendations backed by data from your research. Each recommendation should be under 15 words. Mention specific version numbers or latest release dates when relevant for assessing maintenance status.
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.