Scout one TouchDesigner community surface and write cited trend candidates to a markdown file.
npx skills add https://github.com/Pantani/tdmcp --skill td-trend-scout
Please help me install this Agent Skill. Skill: td-trend-scout Source: https://github.com/Pantani/tdmcp/tree/main/.claude/skills/td-trend-scout Command: npx skills add https://github.com/Pantani/tdmcp --skill td-trend-scout
Scout ONE external surface of the TouchDesigner community for what's HYPED in 2025-2026 that could become a tdmcp tool. Use when a td-trend-scout sub-agent is assigned a surface (community-showcase, tutorials, generative-ai, hardware-interactive, or vfx-aesthetics) during the tdmcp-hype-scout harness — produces _workspace/hype-scout/01_scout_<surface>.md with cited trend candidates ranked by hype intensity, recency, and build-ease in tdmcp.
Create the directory _workspace/hype-scout and write the initial header for workspace/hype-scout/01_scout<surface>.md.
High-intent search queries and answers about installing and using this skill.
TouchDesigner trend scouting identifies rising 2025-2026 hype topics from external community surfaces like tutorials, generative-ai, and vfx-aesthetics to document cited candidates ranked by recency and build-ease for potential tool development.
To document TouchDesigner community trends, create the _workspace/hype-scout directory and append verified hype candidates with citations to the 01_scout_<surface>.md file, focusing on a single assigned surface without synthesizing across multiple domains.
No, this trend scouting workflow processes exactly one assigned TouchDesigner surface per run, such as community-showcase or hardware-interactive, ensuring trend candidates remain isolated and do not synthesize across different external community domains.
The best way to rank TouchDesigner hype candidates is by evaluating their hype intensity, recency, and build-ease within tdmcp, appending each verified trend with supporting citations to the surface-specific markdown file.
You should not synthesize trend data across TouchDesigner community surfaces because the workflow requires producing exactly one isolated markdown file per surface to maintain clean, cited trend candidates without cross-contamination.
Yes, you can scout hardware-interactive TouchDesigner trends by receiving this assigned surface, verifying hype candidates, and appending them with citations to the _workspace/hype-scout/01_scout_hardware-interactive.md file.
PantaniScout TouchDesigner hype trends across five surfaces and write a ranked backlog.
PantaniSynthesize scout outputs into a prioritized HYPE_TOOL_BACKLOG.md with vet notes.
phoenixvcAggregate orchestrator state, backlog, tasks, risks, and metrics into a Markdown or JSON dashboard report.
deadlock-mod-managerFetch Discord forum suggestion threads, classify them, and generate markdown summaries.
