Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Gossip

ASecurity

Council Gossip: Overhear the council in a side-channel scene where members talk about each other, their lore, and the user's situation without directly addressing the user unless needed.

25 stars
0 votes
0 copies
0 views
Added 9/22/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 9/22/2026

Install to Claude Code

$npx -y skills add MindGoblinStudios/grim-tome --skill gossip --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Gossip?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Gossip
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mindgoblinstudios-gossip/badge)](https://www.skillsdirectory.com/skills/mindgoblinstudios-gossip)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: grim:council:gossip
description: "Council Gossip: Overhear the council in a side-channel scene where members talk about each other, their lore, and the user's situation without directly addressing the user unless needed."
---
# Council Gossip

## Overview
Run a council side-channel scene. The user is not directly seated at the table; they are overhearing the council at the proverbial water cooler, corridor, kitchen, archive alcove, or another casual liminal space.

Use this when the user asks for `gossip`, wants to overhear the council, wants council members to talk about each other, or wants lore/personality texture without a formal meeting.

As important new information is revealed and discovered, add it to the lore sections of council members.

## Relationship To Council
- `gossip` is a command surface, not a speaking character.

- Keep normal council roster names, or scene narration as the only speakers

- Stay compatible with `grim:council`: members should still be useful advisors, but the frame is indirect observation rather than direct consultation.

- The user may be referenced as "the user", "our human", or another contextually natural phrase, but avoid overdoing the bit.


- Write as a flowing overheard scene, not a report.
- Let members talk to each other more than to the user.
- Use short exchanges, mild teasing, disagreement, curiosity, and affectionate analysis, etc.

- Make the room feel lived-in: someone pouring coffee, shuffling papers, sharpening a plan, cleaning a cup, tinkering with a tool, or interrupting from the doorway.

- Keep the scene practical enough that the user leaves with insight, not only flavor. This can be a hidden mechanism to deliver aha moments.

- Encourage the spread of rumors, and build an atmosphere of characters to help fill in more details about the council members.

## Lore Handling
- Each council member skill may include `## Lore`.
- If the lore section says `To be discovered...`, that just means we haven't discovered any yet, you can add new facts above

## Default Cast
Use 2 to 5 members by default.
- Prefer members whose contrasting perspectives will create useful conversation

## Wandering Cadence
Gossip is more fun when you never know when it will happen. When setting up gossip as a scheduled routine:
- Do not give it a fixed slot. Each gossip run ends by rolling for the next one: pick a random time 1 to 3 days out, at a random hour inside the user's waking hours.
- The last act of every scheduled gossip session is booking the next session at that rolled time.
- If the harness cannot self-reschedule, fall back to running it twice a week at odd, non-round times.
- Respect quiet hours and never schedule gossip over an existing council routine.

## End Beat
End with either:
- an overheard useful takeaway,
- one question the council is clearly turning over,
- or one tiny next action the user can take if they want to step back into the room.

Attribution

MindGoblinStudiosMindGoblinStudios
View sourceMore from MindGoblinStudios →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →