How do I install the Sense skill?

Run npx skillmds@latest add npbuilds/sense in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sense safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sense?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sense free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

npbuilds (@npbuilds) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sense by npbuilds — Agent Skill

Name: Sense
Author: npbuilds

Sense

Route product sensing work — reading frontier signals through a product lens, detecting emergent capability combinations, interpreting external market and technology signals, and mapping the gap between what's possible and what's surfaced. Activates when the question is "what's becoming possible?" or "what's changing that matters for product?"

npbuilds 5577994 2 files · 4.3 KB Updated Sep 17, 2026

File contents

Sense — The System's Peripheral Vision

The first cognitive mode. Before envisioning, seeding, or surfacing anything, The Loom needs to know what's happening — in the AI frontier, in the skill library's own emergent behavior, in the market, and in the gap between current capability and current exposure.

Sense doesn't decide what to build. It decides what's worth paying attention to.

Child Skills

Skill	Type	When to Route
`frontier-antenna`	action	AI developments, new model capabilities, tool ecosystem changes — through a product lens
`emergence-detector`	action	Unexpected capability combinations in the library, behaviors nobody designed
`signal-reader`	knowledge	External signal interpretation: market timing, adoption curves, technology readiness
`capability-radar`	action	Mapping possible vs. surfaced capabilities, finding the opportunity gap

Routing Logic

Signal	Route To
"What's new in AI that matters for us?"	frontier-antenna
"I noticed something unexpected in the system"	emergence-detector
"Is the timing right?", "adoption curves", "market signals"	signal-reader
"What can we do that we haven't exposed?", "capability gap"	capability-radar
"Give me a full field report"	All four in sequence: frontier-antenna → emergence-detector → capability-radar → signal-reader for synthesis

Curriculum Order

signal-reader (learn the frameworks) → frontier-antenna (apply to AI frontier)
→ capability-radar (map the landscape) → emergence-detector (watch for surprises)

Cross-Domain Interfaces

Child Skill	Engages	For
frontier-antenna	neocortex/frontier-scanner	Raw frontier scan data, translated through product lens
emergence-detector	All domain orchestrators	Monitoring cross-domain interaction patterns
signal-reader	spelunker, archon	Deep research on signals, market timing intelligence
capability-radar	infrastructure-orchestrator, neocortex/architecture	Registry health, gap maps, maturity assessments

Output

The Sense director produces a field report — a structured reading of what's changing, what's emerging, and what demands attention. This feeds directly into the Envision director.

---name: sensedescription: Route product sensing work — reading frontier signals through a product lens, detecting emergent capability combinations, interpreting external market and technology signals, and mapping the gap between what's possible and what's surfaced. Activates when the question is "what's becoming possible?" or "what's changing that matters for product?"---# Sense — The System's Peripheral VisionThe first cognitive mode. Before envisioning, seeding, or surfacing anything, The Loom needs to know what's happening — in the AI frontier, in the skill library's own emergent behavior, in the market, and in the gap between current capability and current exposure.Sense doesn't decide what to build. It decides what's **worth paying attention to**.## Child Skills| Skill | Type | When to Route ||---|---|---|| `frontier-antenna` | action | AI developments, new model capabilities, tool ecosystem changes — through a product lens || `emergence-detector` | action | Unexpected capability combinations in the library, behaviors nobody designed || `signal-reader` | knowledge | External signal interpretation: market timing, adoption curves, technology readiness || `capability-radar` | action | Mapping possible vs. surfaced capabilities, finding the opportunity gap |## Routing Logic| Signal | Route To ||---|---|| "What's new in AI that matters for us?" | frontier-antenna || "I noticed something unexpected in the system" | emergence-detector || "Is the timing right?", "adoption curves", "market signals" | signal-reader || "What can we do that we haven't exposed?", "capability gap" | capability-radar || "Give me a full field report" | All four in sequence: frontier-antenna → emergence-detector → capability-radar → signal-reader for synthesis |## Curriculum Order```signal-reader (learn the frameworks) → frontier-antenna (apply to AI frontier)→ capability-radar (map the landscape) → emergence-detector (watch for surprises)```## Cross-Domain Interfaces| Child Skill | Engages | For ||---|---|---|| frontier-antenna | neocortex/frontier-scanner | Raw frontier scan data, translated through product lens || emergence-detector | All domain orchestrators | Monitoring cross-domain interaction patterns || signal-reader | spelunker, archon | Deep research on signals, market timing intelligence || capability-radar | infrastructure-orchestrator, neocortex/architecture | Registry health, gap maps, maturity assessments |## OutputThe Sense director produces a **field report** — a structured reading of what's changing, what's emerging, and what demands attention. This feeds directly into the Envision director.

Frequently asked questions