Tech Sensemaking

What it does

When your agent uses it

• A new technology
• Capability is announced and you want to understand what new outcomes
• Competitive levers it creates — beyond the obvious hot takes
• : analyze this announcement

Example prompts

• “analyze this announcement”
• “what does this mean for us”
• “tech sensemaking”
• “/tech-sensemaking”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

1. 1Intake
2. 2Context Loading
3. 3VS Generation
4. 4Critique
5. 5Present

What it can do on your machine

Read from SKILL.md and the folder at commit 43a0566. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md.

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Tech Sensemaking loads about 1.8k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 179 tokens; SKILL.md has 765 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~179

When it runs · the whole SKILL.md, loaded when a task matches

~1.8k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~3.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from gnurio/nurijanian-skills at commit 43a0566, republished under its MIT licence (© gnurio). 765 words, ~1,810 tokens.

name

tech-sensemaking

description

Analyze technology announcements to surface non-obvious strategic implications using Verbalized Sampling. Works against any context: a business, product, codebase, feature branch, personal project, career, or exploratory domain. Use when a new technology, feature, or capability is announced and you want to understand what new outcomes, affordances, and competitive levers it creates — beyond the obvious hot takes. Triggers on: "analyze this announcement", "what does this mean for us", "tech sensemaking", "new feature dropped", "what can we do with this", "sensemaking on this", "strategic implications of", or any request to evaluate a technology change strategically. Category: Product Strategy

## Q1: New Outcomes

### High diversity (p < 0.05)
1. [text] (p=0.03, time_horizon: medium, order: second)
   **Reasoning:** [condensed reasoning]

### Moderate diversity (p 0.05–0.10)
2. [text] (p=0.07, ...)
   ...

## Synthesis: Top 3 Moves

[Identify the 3 highest-leverage actions across all 4 questions. For each:]
1. **Action**: What to do
2. **Why now**: Why this announcement creates the window
3. **First step**: The concrete next action

## What I excluded (and why)
[List 2-3 items that were dropped by the critique pass, with the failure reasons.
This shows the user what "obvious" looks like so they calibrate their own thinking.]

© gnurio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/tech-sensemaking of gnurio/nurijanian-skills.

• SKILL.md
• references/vs-prompts.md

Open the folder on GitHubat commit 43a0566