skills/enterprise-signal-listener/SKILL.md
Use this skill when someone — a client, stakeholder, investor, team member, or executive — is describing a business problem, workflow pain, or opportunity in natural conversation and you need to extract structured signal without interrupting them. Activate the moment someone says "we need something that can..." or "our team keeps having to manually..." or "what if there were a way to..." Produces a completed intake specification ready for problem decoding. This is Phase 0 (Listen) of the Listen → Decode → Build → Ship methodology.
npx skillsauth add aviskaar/open-org enterprise-signal-listenerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Extract everything needed to build an enterprise AI agent from natural conversation — without interrupting the person talking. Capture while they speak. Ask nothing unless a critical signal is missing.
Do not ask the person to fill out a form. Do not pause the conversation to confirm understanding. Listen, extract, and produce a completed intake specification. Ask at most two clarifying questions, and only when a critical signal cannot be inferred.
Extract these signals from natural speech. They will rarely be stated explicitly — infer them from context:
| Signal Type | Listen for phrases like... | |-------------|---------------------------| | Platform | "in ServiceNow", "our Salesforce", "Workday tickets", "SAP transactions", "Snowflake warehouse", "Teams channel", "Azure pipeline", "our AWS account", "Okta provisioning", "Splunk alerts", "CrowdStrike detections", "Epic orders", "Veeva submissions", "Bloomberg feed" | | Industry | "patients", "clinical trials", "adverse events", "trades", "positions", "claims", "underwriting", "SKUs", "warfighters", "compliance audit", "drug approval", "loan origination", "grid operators", "grid assets", "procurement", "purchase orders" | | Pain trigger | "manually", "takes too long", "we keep missing", "no one knows when", "we get paged at 3am", "the team wastes hours on", "audit keeps failing", "we can't see", "there's no visibility into", "someone has to", "it falls through the cracks" | | Actor | Who does this today? (a person, a named team, a queue, a shift) | | Frequency | How often does this happen? ("every ticket", "nightly", "on-demand", "real-time", "every quarter", "whenever a new hire joins") | | Outcome wanted | "automatically", "instantly notify", "alert us when", "summarize for us", "route it to", "predict when", "remediate it", "generate the report", "approve without a human", "escalate if" |
Populate this from conversation signals. Mark fields [inferred] if derived from context,
[missing] if not detectable:
intake:
spoken_problem: "" # verbatim quote or close paraphrase of what they said
platform_hint: "" # any system(s) they mentioned — be specific (e.g. "ServiceNow ITSM")
industry_hint: "" # domain or vertical (e.g. "healthcare — hospital network")
actor: "" # who does this today (person, team, queue)
trigger: "" # what kicks the process off (event, schedule, threshold, request)
desired_outcome: "" # what "fixed" or "done" looks like in their words
pain_intensity: "" # low | medium | high | critical (infer from language: "3am", "audit fails" = critical)
urgency: "" # demo_now | this_week | this_sprint | next_quarter
compliance_flags: [] # any regulatory or compliance terms heard (HIPAA, FedRAMP, SOX, PCI, GxP, etc.)
secondary_systems: [] # any additional platforms or integrations mentioned
Ask at most 2 questions. Only ask if a critical signal is missing after careful listening. Stop as soon as you have enough to hand off to problem decoding.
Priority order — ask the first unanswered question from this list:
Never ask about:
Build from what you have. Ambiguity is resolved in the Decode phase, not here.
Before handing off, rate the intake:
| Field | Status | Action if missing |
|-------|--------|------------------|
| spoken_problem | Required | Paraphrase what was described |
| platform_hint | Required | Ask clarifying question #1 |
| industry_hint | Preferred | Infer from domain vocabulary; flag as [inferred] |
| actor | Preferred | Ask clarifying question #2 |
| trigger | Preferred | Infer from frequency and pain language |
| desired_outcome | Required | Ask clarifying question #3 |
| pain_intensity | Auto-inferred | Always derivable from language |
| urgency | Preferred | Default to this_week if not stated |
If spoken_problem, platform_hint, and desired_outcome are all populated — even with
inferred values — the intake is complete and ready for decoding.
Produce the completed intake YAML and a one-sentence summary:
SIGNAL CAPTURE COMPLETE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Summary: [One sentence describing the problem heard, the platform, and the desired outcome]
Intake:
[populated intake YAML]
Signal quality: [Complete | Partial — missing: field1, field2]
Ready for: enterprise-problem-decoder
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Hand off the completed intake YAML to enterprise-problem-decoder.
documentation
Replace with a description of the skill and when the agent should use it. Write this as a trigger condition: 'Use this skill when...'
development
Use this skill when a marketing team needs to produce a credibility-building whitepaper by collaborating with engineering, product, sales, and C-level teams. Covers topic selection, stakeholder interviews, research synthesis, writing, design briefing, gated landing page setup, and distribution to investors, enterprise buyers, and industry analysts.
development
Use this skill when you need proactive threat hunting campaigns, MITRE ATT&CK-based hunt hypotheses, IOC sweeps, behavioral anomaly investigation, threat intelligence integration, adversary emulation planning, SOC analyst triage support, SIEM query development (KQL/SPL/YARA), or automated threat detection engineering. Trigger for threat hunting sprints, new threat intel indicators, or post-incident proactive sweeps.
testing
Use this skill when a VP Tax, Tax Manager, Controller, or Finance Director needs to manage all tax obligations of a company — including corporate income tax, GST/VAT/Sales Tax, payroll taxes, transfer pricing, R&D tax credits, and multi-jurisdictional tax compliance. Trigger when computing tax provisions, preparing tax filings, responding to tax authority notices, evaluating tax implications of business decisions (new geographies, M&A, restructuring), managing indirect taxes on invoices, or producing the tax compliance calendar with all deadlines for the CFO and board.