RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), GitHub, YouTube, LinkedIn, and Amazon. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[numman-ali/openskills] Read skill.json from source repos for install and sync

The user requests that OpenSkills should read skill.json from source repositories to improve the installation and synchronization process, especially for large repositories.

Original Source

@@xtfer | 0 pts | 3/6/2026

### Problem OpenSkills discovers skills in two places where filesystem scanning creates friction: 1. **Install** — `openskills install anthropics/skills` clones the repo, walks the directory tree to find SKILL.md files, and presents them in an interactive TUI for selection. On large repos this scan is slow, and there's no structured metadata (categories, tags) available to help users pick the right skills. 2. **Sync** — `openskills sync` reads installed skills' SKILL.md frontmatter to generate the `<available_skills>` XML block in AGENTS.md. It can only emit `name` and `description` because that's all SKILL.md frontmatter provides. Richer metadata (categories, tags, version) would improve agent skill routing but isn't available today. ### Proposed Solution Support reading an optional `skill.json` (singular) from the root of source repos. When present, use it as the primary source of skill metadata for both install and sync. Example `skill.json` in a source repo: ```json { "nam

Discussion

Loading comments...