detect-thoughts

Extract explicit goals and unspoken priorities from messages into structured intent analyses.

105|13|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Hmbown/Wizards-of-the-Ghosts --skill detect-thoughts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: detect-thoughts
Source: https://github.com/Hmbown/Wizards-of-the-Ghosts/tree/main/generated/hermes/investigation-and-preparation/detect-thoughts
Command: npx skills add https://github.com/Hmbown/Wizards-of-the-Ghosts --skill detect-thoughts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In D&D, Detect Thoughts lets you read surface thoughts and probe deeper. The real-world version is intent analysis: figuring out what someone is trying to accomplish based on what they said, how they said it, and what they chose not to say. This is the analytical complement to Insight (which reads subtext intuitively) — Detect Thoughts is more structured and systematic. This Skill provides a principled method to extract priorities, concerns, and unstated goals from communications, making conversations and requirements more actionable.

Core Features & Use Cases

  • Intent extraction: identify explicit goals, priorities, and concerns from text.
  • Gap mapping: highlight divergences between stated objectives and inferred real priorities.
  • Actionable recommendations: produce response or negotiation guidance aligned with inferred intent.
  • Use Case: before a requirements review, analyze a message from a stakeholder to surface what they truly want, what they care about most, and what they are likely not stating directly.

Quick Start

Provide a structured intent analysis from a given message, including explicit priorities, potential concerns, and recommended response.

Frequently Asked Questions about detect-thoughts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze intent and priorities from a stakeholder message?

To analyze intent from a message, you extract explicit goals and map unstated priorities by examining communication signals. This structured intent analysis identifies what a stakeholder truly wants and highlights gaps between stated objectives and inferred real priorities.

What is intent analysis and gap mapping in communication?

Intent analysis is the process of reading surface-level messages to extract goals, concerns, and unstated priorities. Gap mapping highlights divergences between these stated objectives and inferred real priorities, making conversations and project requirements more actionable.

Can I use this to surface unspoken priorities before a requirements review?

Yes, you can surface unspoken priorities before a requirements review by analyzing a stakeholder's message. The process identifies what they truly want, what they care about most, and what they are likely not stating directly across project scenarios.

What is the best way to map inferred intents to concrete actions?

The best way to map inferred intents to concrete actions is through a structured deliverable. This approach provides intent analysis, gap analysis, and recommended responses with confidence levels and assumptions tailored for negotiation or project scenarios.

How does structured intent analysis differ from intuitive subtext reading?

Structured intent analysis differs from intuitive subtext reading by providing a systematic, principled method to extract priorities and concerns from text. It maps likely intents to concrete actions rather than relying on intuitive interpretation of communication signals.

What limitations exist when analyzing unstated goals from brief messages?

When analyzing unstated goals from brief messages, confidence levels and underlying assumptions must be explicitly stated. Limitations arise from missing context, requiring the analysis to map likely intents based solely on available communication signals rather than confirmed facts.