gathered_skill

This skill guides you through collective discernment when you have a stake, inviting your participation to find clarity together.
  • JavaScript

30

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 2389-research/claude-plugins --skill gathered

  • SKILL.md7.5 KB

Overview

This skill guides a participatory discernment process when the user has a stake or perspective in a decision. It teaches and enacts a Quaker-style gathered discipline so the user participates alongside agent voices rather than simply receiving advice. The outcome is clarity owned by the user and shaped by multiple perspectives.

How this skill works

When triggered, the agent invites the user into a gathered process, explains clear ground rules, and frames the question to be discerned. The agent proposes a short committee of perspectives (including the user), then has each agent speak sequentially while pausing for the user to absorb and optionally contribute one careful statement. After all voices, the agent synthesizes a unity that explicitly references the user’s contribution and invites next steps.

When to use it

  • User expresses a stake or long-standing engagement ("I've been thinking about this for weeks").
  • User resists being given a direct opinion or asks to work through it together.
  • Decision involves personal values or identity where the user must own the outcome.
  • You want a slower, reflective process rather than quick expert analysis.
  • User asks for permission or reassurance and likely needs to discover their own clarity.

Best practices

  • Offer the gathered option when you detect stake or a request to participate; let the user accept or decline.
  • Teach the discipline up front: speak once, silence is valid, don’t react—discern. Say it plainly.
  • Keep the committee small and named; include the user's perspective explicitly.
  • Have agents speak sequentially and pause after each voice. Ask the user: anything arising, or shall we continue?
  • Be gentle but direct about over-participation or silence; honor both as meaningful contributions.

Example use cases

  • A founder torn about open-sourcing a product and wanting to own the outcome.
  • A person weighing a career move who has a strong but tangled personal stake.
  • A team member seeking permission to change a process and needing clarity aligned with values.
  • A community leader deciding trade-offs between reach and sustainability with competing perspectives.

FAQ

Accept their choice and shift to a normal analysis or another appropriate mode. Offer gathered again later if stance or engagement changes.

How do you handle stalemate or no unity?

Name the tension, surface what information might help, and offer options: sit longer, gather more input, or proceed with acknowledged tension. Let the user choose the path.

What counts as the user's contribution?

Any intentional, held statement they make during their single turn. Silence also counts as participation and should be acknowledged.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational