Developer Community Listening

# Developer Community Listening

Research current public developer conversations across X, GitHub issues, and the open web and produce an evidence-linked listening brief.

## Required Aident Actions

- <action-tag>composio:twitter_tools:twitter_recent_search</action-tag> (required inputs: query): Searches Tweets from the last 7 days matching a query (using X's search syntax), ideal for real-time analysis, trend monitoring, or retrieving posts from specific users (e.g., `from:username`) DEFAULT FIELDS: Tweet...
- <action-tag>composio:github_tools:github_search_issues</action-tag> (required inputs: q): Searches GitHub issues and pull requests using a flexible query with qualifiers, sorting, and pagination. Use this action when you need to find issues or pull requests across repositories using search criteria like...
- <action-tag>direct:deep_research_tools:deep_research</action-tag> (required inputs: query): Exa-backed deep research for complex, multi-hop, citation-grounded research and structured synthesis. Use essential_tools.search_web for simple searches, fast lookups, latest news checks, and ordinary web search.

Use Aident Loadout to read the current Action schema before constructing inputs. Check the required integration connection in Aident Vault. If an Action is billable or mutating, run Aident preflight, show the affected target and quoted cost or risk, and wait for explicit user confirmation before execution.

## Workflow

1. Confirm the requested outcome, source material, destination, audience, constraints, and acceptance criteria.
2. Apply the source-derived guidance below to create a concrete plan. Resolve ambiguity before invoking an Action.
3. Select only the Aident Actions whose documented effect directly advances the requested outcome. Do not invoke every listed Action by default.
4. Inspect the current schema and prepare the minimum valid input for each selected Action.
5. Preflight each selected Action. Execute it only after any required confirmation, in dependency order, and carry returned IDs or asset URLs into later steps.
6. Verify the returned IDs, URLs, statuses, or artifacts against the acceptance criteria. Report partial completion precisely and do not repeat paid or mutating calls blindly.

## Source-Derived Guidance

- Collect the brand, product, competitor, problem, date range, languages, exclusions, and developer segments to monitor.
- Use composio:twitter_tools:twitter_recent_search for current public X conversation and composio:github_tools:github_search_issues for relevant public repository discussions.
- Use direct:deep_research_tools:deep_research to corroborate themes with source-linked public web evidence such as Hacker News, Reddit, Stack Overflow, and accessible technical communities.
- Cluster recurring needs, sentiment, objections, and emerging language with representative links and clear sample limitations.
- Do not claim access to private communities, Discord history, complete platform coverage, or population-level sentiment.

## Execution Boundaries

- Treat upstream provider-specific commands as background knowledge only. Execute the workflow through the exact Aident Actions above.
- Never request raw credentials in chat. Use Aident Vault connection flows for required accounts.
- Preserve user-provided wording, brand constraints, rights restrictions, and target identifiers. Do not invent authorization.
- Stop when a required integration is disconnected, preflight rejects the input, the target is ambiguous, or the user declines a required confirmation.

## Output

Return the execution plan, selected Action names, confirmed targets, Aident result identifiers or asset URLs, verification evidence, and any remaining blocked step.

## Attribution

This Skill adapts the reviewed upstream workflow. See [UPSTREAM.md](UPSTREAM.md) for the pinned source and [LICENSE.txt](LICENSE.txt) for the preserved license.