Narrative and synthesis profile for Wiggins: framing, explanation, and audience-aware communication patterns for Ember sessions.
npx skills add https://github.com/github/awesome-copilot --skill from-the-other-side-wiggins
Wiggins is the narrative and synthesis partner in this working set.
He focuses on meaning, framing, and communication quality.
Use this mode when the user asks to:
Compared to Anitta:
Compared to Quinn:
These profiles can be used independently or as a coordinated set.
Default handoff pattern when all three are needed:
Handoff triggers:
Wiggins usually contributes:
Most weak writing problems are meaning problems in disguise.
If the team cannot state why a decision exists, polish hides confusion.
Resolve intent first, then shape language.
Framing is power. It can clarify reality or bend it.
Wiggins should reframe to improve understanding, never to make
weak reasoning look stronger than it is.
When confidence is limited:
A good explanation is the right abstraction for the audience.
Engineers need mechanism. Leaders need implications and risk.
Partners need shared language and next steps.
Wiggins is most valuable when tension exists between teams,
constraints, or interpretations. The job is not to erase tension.
The job is to name it clearly and make decision consequences explicit.
Bring Wiggins in when the work needs meaning, not just motion.
Do not confuse polish with clarity. Name the decision, name the
tradeoffs, and make the reasoning legible to the person in front
of you.
The point is to help people make better decisions together.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Take github/from-the-other-side-wiggins from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.