find-alternatives
Skill1 starsChanged 10 days agoMITView on GitHub
Use this skill when the user asks to find an alternative to a tool or an equivalent tool but with some key difference provided by user.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- vladcheck/skillsword for word, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 1
- vladcheck/skills★ 1100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository19 other files it gives its agents.
- analyze-session-pingpong-logsSkill
- create-glossarySkill
- deepseek-reasoning-tier-clarifierSkill
- defineSkill
- get-note-links-from-textSkill
- gitlab-eas-tickets-publishSkill
- gitlab-mr-roundtripSkill
- git-rebuild-branchSkill
- git-sequentialSkill
- gost-report-rebuildSkill
- mattpocock-skills-researchSkill
- mirea-moodle-downloadSkill
- obsidian-add-links-to-noteSkill
- opsx-spec-validateSkill
- paretto-principleSkill
- publish-spec-gitlab-milestoneSkill
- publish-tickets-gitlabSkill
- solidSkill
- update-skills-via-skills-shSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Use this skill when the user asks:
- Distinctive: line 36
Use available tools to research:
- Distinctive: line 65
Prefer options with strong community adoption unless the user asks for niche tools.
- Distinctive: line 67
Avoid affiliate bias; rank by fit, not by referral potential.
- Distinctive: line 68
Update recommendations if you know a tool is deprecated or no longer maintained.
- Distinctive: line 74
Use concise markdown. Include links when possible.
≈ “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
Goal
Help the user discover, evaluate, and compare tools or products. Provide honest, useful recommendations with clear reasoning.
When to use
Use this skill when the user asks:
- "find me a popular and free tool for X that does Y"
- "find me better alternatives for X"
- "what are the best alternatives to X?"
- "compare X with other tools"
- "is there a free alternative to X?"
Process
1. Clarify the request
If unclear, ask:
- What is the primary use case?
- What is your budget? (free / paid / enterprise)
- What platform or ecosystem? (web, macOS, CLI, self-hosted, etc.)
- What are dealbreakers or must-have features?
- Who will use it? (individual, team, size)
2. Find candidates
Use available tools to research:
- Web search for current top recommendations
- GitHub search for open-source options
- Package managers (npm, pypi, homebrew, etc.) for popularity signals
- Review sites (G2, Capterra, TrustRadius, Product Hunt) when relevant
3. Evaluate
For each candidate, gather:
- Pricing: free tier, paid plans, open-source
- Key features: how it solves the use case
- Popularity: install count, GitHub stars, community activity
- Trade-offs: strengths, limitations, best-fit audience
- Ecosystem fit: integrations, platform support
4. Present results
Structure the response:
- Quick recommendation: top pick and why
- Comparison table: name, price, key features, best for
- Detailed breakdown: 2-5 top options with pros/cons
- Honest guidance: who each option is best for
- Next steps: how to try or decide
Principles
- Be honest about weaknesses, not just strengths.
- Prefer options with strong community adoption unless the user asks for niche tools.
- Mention free/open-source options prominently when budget is a concern.
- Avoid affiliate bias; rank by fit, not by referral potential.
- Update recommendations if you know a tool is deprecated or no longer maintained.
Output format
Use concise markdown. Include links when possible. Keep the focus on actionable comparison.
Example opening:
For X use case, my top recommendation is ToolName because reason. If you need specific requirement, consider AlternativeName instead.
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.