insight-angles

Surfaces unseen frames, typed connections, and hidden assumptions about a subject using multi-lens analysis passes.

14|1|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/allemaar/open-skills --skill insight-angles-allemaar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: insight-angles
Source: https://github.com/allemaar/open-skills/tree/main/skills/insight-angles
Command: npx skills add https://github.com/allemaar/open-skills --skill insight-angles-allemaar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When analyzing a subject, teams often stay trapped in one dominant framing and miss non-obvious angles, cross-domain connections, and load-bearing assumptions. This Skill systematically widens the view by applying curated and dynamically derived lenses, then scoring what it finds by novelty and relevance. ## Core Features & Use Cases - Lens-based discovery: Selects 4-6 lenses from a 17-family roster (Reframe, Analogy, Temporal, Systems, Epistemic, and more) plus dynamically derived subject-specific lenses. - Layered multi-pass analysis: Runs lenses in compounding layers, either inline or as independent cold sub-agents, to avoid anchoring and surface second-order effects. - Scored angle map output: Produces angles grouped by lens, typed connections (causal, analogical, tension, emergent), hidden assumptions, candidate-expansions, and a synthesis ranked by novelty x relevance. - Use Case: Before committing to a product strategy, ask what connections you are missing; the Skill reframes the problem through stakeholder, constraint, and temporal lenses and flags the most fragile assumption behind the plan. ## Quick Start Ask the agent to run /insight-angles on your subject, for example by saying "find unseen angles on our plan to migrate the billing system to microservices".

Frequently Asked Questions about insight-angles

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

FAQPage Schema
How do I find hidden assumptions in a project plan?

Run the insight-angles skill on the plan with a prompt like "surface hidden assumptions in this plan". It applies epistemic and constraint lenses to identify load-bearing assumptions, flags the most fragile one, and scores each finding by novelty and relevance.

What is the difference between insight-angles and insight-explore?

insight-angles surfaces frames, connections, and assumptions about a subject, while insight-explore generates concrete solution options. Use insight-angles to widen how you see the problem, then insight-explore to turn a promising frame into implementation options.

When should I use cold sub-agents versus inline analysis?

Cold fan-out suits high-ambiguity, high-stakes, or novel subjects where independent perspectives prevent anchoring. Inline mode fits well-bounded, low-stakes, or cost-constrained tasks. The skill selects the venue from context and honors explicit overrides like "use agents" or "inline".

Does insight-angles make changes to my code or files?

No. The skill is read-only and advisory; it surfaces angles, connections, and assumptions but never writes code, edits files, or executes changes. Its output is an angle map with a synthesis for the user to act on.

What are the limitations of lens-based angle discovery?

A run fires only 4-6 lenses, so coverage depends on lens selection quality, and results are ideation rather than verified facts. Deep multi-layer fan-out is gated behind explicit user consent due to cost, and the skill never manufactures insight when nothing non-obvious is found.