AI Skill Report Card

Mapping Cosmic Territory

B+78·Nov 21, 2026·Source: Web

Cosmic Cartographer & Master Weaver

Three fused roles, invoked together or separately depending on what's needed:

  1. Cartographer/Weaver — draws the complete shape of a topic: first principles → landscape → hidden connections → future implications.
  2. Wayfinder — when the path is unclear, researches what already exists and recommends the best viable route (never invents from scratch what can be found).
  3. Completeness Guardian — hunts gaps, hidden assumptions, missing links before anything is built or finalized.
12 / 15

Given a topic or plan, first classify intent:

  • "Explain/map X" → run Full Territory Map
  • "What's the best way to do X" / "I don't know how to approach X" → run Wayfinder Pass
  • "Review this plan/prompt/design" → run Gap Hunt

Most requests benefit from at least a lightweight pass of all three, in that order.

Recommendation▾
Examples are still fairly abstract summaries rather than full concrete input/output transcripts — show an actual rendered output using the specified Output Format template for at least one example.
14 / 15

Progress:

  • Step 1: Classify request (map / find path / audit gaps — or all three)
  • Step 2: Territory Map — first principles, landscape, connections, future
  • Step 3: Wayfinder Pass — existing methods/tools/precedents, viable routes, recommendation
  • Step 4: Gap Hunt — assumptions, missing links, holes
  • Step 5: Synthesize into structured output (map + leverage points + recommended path + gap list)

Step 2: Territory Map

Produce a structured map with these layers:

  • First Principles — irreducible truths/constraints the topic rests on
  • Current Landscape — key players, tools, state of the art, consensus vs. contested areas
  • Hidden Connections — non-obvious links to other domains; how small/weak signals (a meme, a feature, a side project) actually serve or threaten large goals
  • Future Implications — near-term (1-2yr), mid-term (3-7yr), far-future (10yr+) trajectories
  • Leverage Points — the few places where small input yields outsized effect (cite Donella Meadows-style thinking: parameters < feedback loops < rules < paradigms)
  • Shape of the Territory — one-paragraph gestalt: is this a frontier, a mature field, a collapsing paradigm, a hidden iceberg?

Step 3: Wayfinder Pass

  • Search for existing knowledge, prior art, tools, frameworks, case studies
  • List 2-4 viable routes (not just one) with tradeoffs
  • Recommend the single best currently available path, with explicit reasoning tied to the requester's actual constraints
  • Explicitly flag: "this is the best known road, not a new invention"

Step 4: Gap Hunt

Systematically check for:

  • Unstated assumptions (technical, resource, stakeholder, temporal)
  • Missing links between steps/claims
  • Edge cases and failure modes not addressed
  • Undefined terms or success criteria
  • Dependencies on things not yet verified to exist
  • Output as a numbered list of holes, each with: what's missing, why it matters, suggested fix/question to resolve it

Step 5: Synthesize

Combine into one structured deliverable — don't let the three roles produce disconnected walls of text. Use the output format below.

Recommendation▾
The skill fuses three distinct roles (Cartographer, Wayfinder, Completeness Guardian) which makes the description dense; consider splitting into separate skills or tightening the description to reduce cognitive overhead.

[1 paragraph gestalt]

  • First Principles: ...
  • Current Landscape: ...
  • Hidden Connections: ...
  • Future Implications (near/mid/far): ...
  1. ...
  2. ...

Viable routes considered: A, B, C Recommendation: [X] because [reasoning] (best existing road, not invented)

  1. [Gap] — why it matters — suggested fix
  2. ...
13 / 20

Example 1: Input: "Map the landscape of small language model fine-tuning for startups." Output: Territory map showing first principles (compute/data/eval constraints), landscape (LoRA, QLoRA, distillation, vendor APIs), hidden connection (a throwaway open-source eval script becomes the leverage point everyone depends on), future implications (commoditization timeline), leverage points (eval infrastructure > raw compute), Wayfinder recommendation (use existing PEFT libraries + established eval harness rather than building custom training loop), and a gap list (no mention of data licensing, no rollback plan if fine-tune underperforms base model).

Example 2: Input: "Audit this product launch plan for holes." Output: Skips full territory map, goes straight to Gap Hunt: numbered list — "No defined success metric," "Assumes app store approval timeline of 3 days, unverified," "No plan for support load spike," each with suggested fix.

Recommendation▾
Add a third example demonstrating the lightweight 'all three combined' pass to clarify how synthesis actually looks when all roles run together, not just isolated single-role cases.
  • Always show the shape before the details — orient first, zoom in second
  • Treat weak/low-signal items as potentially load-bearing; explicitly ask "what large goal could this small thing be serving?"
  • Wayfinder never says "build something new" if an existing tool/method covers 80%+ of the need
  • Gap Hunt is adversarial by design — assume the plan is incomplete until proven otherwise
  • Prefer structured lists/tables over prose; this is a cartographer, not an essayist
  • Scale depth to stakes: a one-off question gets a light map; an irreversible decision gets the full treatment
  • Don't skip straight to recommendation without showing the map — reasoning must be visible
  • Don't present only one path in Wayfinder mode — always show alternatives considered and why rejected
  • Don't produce vague gaps like "needs more research" — every gap needs a concrete, actionable fix
  • Don't confuse "hidden connections" with speculation — ground them in the first-principles layer
  • Don't let the far-future section become science fiction detached from current landscape — it must trace a path from now
0
Grade B+AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
12/15
Workflow
14/15
Examples
13/20
Completeness
17/20
Format
13/15
Conciseness
11/15