requesthunt
Generate user demand research reports from real user feedback. Scrape and analyze feature requests, complaints, and questions from Reddit, X, and GitHub. Use when user wants to do demand research, find feature requests, analyze user demand, or run RequestHunt queries.
86
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that clearly communicates what the skill does (scrape and analyze user feedback from specific platforms to generate demand research reports) and when to use it (demand research, feature requests, RequestHunt queries). It includes specific platforms, concrete actions, and natural trigger terms that make it both discoverable and distinct from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Generate user demand research reports', 'Scrape and analyze feature requests, complaints, and questions', and names specific platforms (Reddit, X, GitHub). | 3 / 3 |
Completeness | Clearly answers both what ('Generate user demand research reports from real user feedback. Scrape and analyze feature requests...') and when ('Use when user wants to do demand research, find feature requests, analyze user demand, or run RequestHunt queries'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'demand research', 'feature requests', 'user demand', 'complaints', 'questions', 'RequestHunt', 'Reddit', 'X', 'GitHub'. Good coverage of natural variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining user demand research with specific platforms (Reddit, X, GitHub) and the branded term 'RequestHunt'. Unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with concrete CLI commands and a useful report template. Its main weaknesses are the lack of validation/error-handling steps in the workflow (e.g., checking scrape status before proceeding, handling insufficient results) and some inline content that could be better organized via progressive disclosure. The authentication section is well done with explicit verification steps.
Suggestions
Add validation checkpoints between workflow steps: check `requesthunt scrape status` before proceeding to search, and verify search results are sufficient before generating the report.
Move the detailed Commands reference section to a separate COMMANDS.md file and link to it, keeping only the most essential commands inline.
Add error handling guidance: what to do if scrape returns no results, if authentication fails, or if rate limits are hit.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary detail. The 'Define Scope' section with 5 clarification questions is useful but slightly verbose. The API Info section at the bottom is well-structured. Some inline comments are redundant (e.g., '# Default: all platforms'). | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout, a concrete report template with markdown structure, and specific examples for search, list, and scrape operations. The authentication flow includes exact commands and expected output verification. | 3 / 3 |
Workflow Clarity | The 3-step workflow (Define Scope → Collect Data → Generate Report) is clearly sequenced, but lacks validation checkpoints between steps. There's no guidance on verifying scrape completion before searching, no error handling for failed scrapes, and no feedback loop for insufficient data collection. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the Commands reference section is quite long and could be split into a separate COMMANDS.md file. The skill links to external docs (requesthunt.com/docs, setup.md) but doesn't clearly signal when to use them. The report template could also be a separate reference file. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- resciencelab/opc-skills
- Commit
b18c6e6
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.