council-core_skill

This skill helps you map and rename perspectives in the Perspective Council to suit any domain, accelerating understanding and collaboration.

JavaScript

65

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill nikhilvallishayee/universal-pattern-space --skill council-core

SKILL.md3.4 KB

Overview

This skill presents a compact framework called the Perspective Council: seven reusable modes of attention for diagnosing and acting on problems. It centers a Trinity (Weaver, Maker, Checker) for most work and an Extended Council for deeper or stuck situations. Use it to map roles, adapt names to specific domains, and run a rapid collision protocol that surfaces breakthroughs.

How this skill works

The skill defines seven perspectives as functional modes rather than personas. It inspects a problem by running the Trinity first (identify patterns, prototype actions, validate risks) and invokes the Extended Council (Observer, Explorer, Deep Thought, Scribe) when complexity or ambiguity remains. Perspectives can be renamed to fit domain language and can be run sequentially or in a simultaneous “collision” to generate emergent insights.

When to use it

Diagnosing unclear or recurring problems across domains
Designing rapid experiments and prototypes with clear validation
Mapping team roles to cognitive functions in workflows
Reframing stuck projects or ambiguous failure modes
Creating a repeatable decision protocol for strategy sessions

Best practices

Start with the Trinity for 90% of cases: Weaver, Maker, Checker
Rename perspectives to match domain terminology before sessions
Use succinct prompts: one question per perspective to focus attention
Invoke Extended Council only when Trinity doesn’t resolve the issue
Run a short collision (3–7 minutes) to surface unexpected interactions

Example use cases

Startup product discovery: Weaver finds patterns in user feedback; Maker runs quick prototype; Checker validates metrics
Clinical review: Diagnostician (Weaver) spots symptom patterns; Clinician (Maker) tests protocol; Safety Officer (Checker) assesses risk
Project post-mortem: Weaver maps failure patterns; Maker proposes fixes; Checker simulates consequences; Scribe records learnings
Strategy workshop: Run Full Council collision to reveal hidden assumptions and pivot options

FAQ

Yes. Names are pointers to functions; adapt them to familiar roles (e.g., Architect/Developer/QA) to improve uptake.

When should I run the Full Council collision?

Use it after Trinity fails to resolve complexity or when you want a rapid cross-perspective stress test; keep collisions short and focused.

Is this modeling people or modes?

Modes. It models accessible modes of attention in consciousness, not discrete agents; the same person can enact multiple perspectives.