prospecting-signal-context-builder

Normalize fragmented GTM notes into a structured signal-context.md file.

10|1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/marcocello/dot-codex --skill prospecting-signal-context-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prospecting-signal-context-builder
Source: https://github.com/marcocello/dot-codex/tree/main/skills/prospecting-signal-context-builder
Command: npx skills add https://github.com/marcocello/dot-codex --skill prospecting-signal-context-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns scattered product, market, ICP, competitor, and engagement notes into a single reusable signal-context.md file for prospecting signal detection. It helps teams avoid inventing assumptions by keeping unknowns explicit and tying search and engagement rules to source material only.

Core Features & Use Cases

  • Normalize GTM context: Organize product context, sector context, ICP details, competitors, pain points, triggers, and constraints into a consistent structure.
  • Create detector-ready output: Produce a concise markdown file that prospecting-signal-detector can scan quickly for prospecting workflows.
  • Handle incomplete inputs safely: Preserve missing details as Unknown or Needs input, surface open questions, and avoid unsupported claims.
  • Use Case: A sales ops team provides call notes, positioning docs, and competitor references, and the Skill converts them into a clean signal-context.md for future signal scanning.

Quick Start

Give me the relevant notes or files for your product and market context, and I will turn them into a workspace-root signal-context.md for prospecting signal detection.

Frequently Asked Questions about prospecting-signal-context-builder

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

FAQPage Schema
How do I normalize fragmented GTM notes into a structured signal context file?

You can normalize scattered GTM notes into a structured signal context by providing positioning documents, call notes, and competitor references. The Skill extracts source-grounded details and outputs a reusable markdown file for prospecting workflows.

What is signal context for prospecting signal detection?

Signal context is a structured markdown file containing normalized ICP details, pain points, triggers, and constraints. It provides reusable detection inputs and qualification rules tied strictly to source material.

How do I handle incomplete ICP details and competitor information during context normalization?

When handling incomplete ICP details during context normalization, this Skill preserves missing details as Unknown or Needs input, surfaces open questions, and avoids unsupported claims to prevent invented assumptions.

Can I use call notes and positioning docs to create detector-ready prospecting rules?

Yes, you can use call notes and positioning docs to create detector-ready prospecting rules. The Skill converts these fragmented inputs into a concise markdown file that signal detectors can scan quickly for qualification and search seeds.

What are the limitations of using markdown for signal context normalization?

A limitation of using markdown for signal context normalization is that it requires strict source-grounded extraction, meaning it will not generate unsupported claims and will leave gaps as Unknown if source inputs are incomplete.