# Community Research

> Community sources — Hacker News, issues, forums, and discussions. Use for practitioner sentiment, failure reports, and what actually broke for real users.

- Skill: `samraddhashrivastavatech/community-research` (Agent Skill)
- Install (CLI): `npx skillmds@latest add samraddhashrivastavatech/community-research`
- Raw SKILL.md: https://api.skillmd.com/api/skills/samraddhashrivastavatech/community-research/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- Author: SAMRADDHASHRIVASTAVATECH (https://skillmd.com/u/samraddhashrivastavatech)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/samraddhashrivastavatech/community-research

---


# Community research

Mine practitioner communities for real-world experience: HN threads, issues,
forums.

## When to use

- "Does this actually work in practice?" — real-user reports.
- Characterizing pain points, workarounds, and adoption sentiment.
- Enriching error investigation with what others hit before.

## Tools used

- `search_community` — query across hackernews/github community surfaces.

## Workflow

1. Ask the question the community can answer (real usage, failures, opinions).
2. `search_community`; note the platform each result came from.
3. Separate signal (reproducible failures, dates, versions) from noise
   (unverified anecdotes).
4. Fold findings into the research with explicit "community-reported" labeling.

## Input schema

```json
{ "query": "str", "limit": "int" }
```

## Output schema

```json
{ "results": "list[{title,url,platform,relevance}]" }
```

## Security

Anecdotes are evidence of experience, not of truth or frequency. Aggregate
before summarizing; never present one report as consensus.

## Related skills

`error-investigation`, `github-research`, `web-search`, `source-analysis`,
`contradiction-search`