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

Team Decide

ASecurity

Record the conclusion of a team-comms discussion and close the thread. Use when a discussion has reached an answer, when the user says what was decided, or when a thread is finished and should stop appearing as live.

2 stars
0 votes
0 copies
0 views
Added 9/20/2026
developmentrustgobashnodedocumentation

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add atman-33/workhub --skill team-decide --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Team Decide?

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

Security grade badge for Team Decide
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/atman-33-team-decide/badge)](https://www.skillsdirectory.com/skills/atman-33-team-decide)

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

Download Zip
Files
SKILL.md
---
name: team-decide
description: Record the conclusion of a team-comms discussion and close the thread. Use when a discussion has reached an answer, when the user says what was decided, or when a thread is finished and should stop appearing as live.
---

# Record a decision and close the thread

A thread nobody closes keeps showing up as live, and the team stops trusting
the list. Closing is cheap — two posts.

## Steps

1. **Make sure you have the discussion**, not just the last message: run
   `team-catchup` if this session is cold. The decision post has to say what
   was rejected, and that is in the middle of the thread.

2. **Post the decision:**

   ```bash
   node "${CLAUDE_PLUGIN_ROOT}/scripts/comms.mjs" post \
     [--thread <id>] --kind decision \
     --summary "<what was decided, in one line>" [--body-file <path>]
   ```

   The body carries what a reader in three months needs: what was chosen, the
   reason, what was rejected and why, and anything left open. That paragraph is
   the entire value of having discussed it in writing.

3. **Close it:**

   ```bash
   node "${CLAUDE_PLUGIN_ROOT}/scripts/comms.mjs" post \
     [--thread <id>] --kind status --state closed --summary "<why it is closed>"
   ```

   Closed threads drop out of `comms list` and clear their own focus at the
   next session start.

4. **Check for a competing decision first.** If the thread already has one,
   the tools report "several decisions" rather than resolving it — because sync
   delay lets two people each believe theirs was last. Do not add a third
   silently: say what is already recorded, and let the user settle it.

5. **Carry the conclusion where it belongs.** A decision that changes how a
   repository works belongs in that repository too — an ADR, a rule, or the
   project's own notes. The thread is the discussion, not the documentation.

## Rules

- **Only record what the team actually settled.** Writing a decision to tidy
  away a thread that is still open is worse than leaving it open.
- Anyone may close a thread and everything stays in the history, so an undo is
  just another status post. The convention is that whoever opened it closes it.
- Never close a thread that is waiting on somebody's answer, even if it has
  gone quiet. Mention them instead.

Attribution

atman-33atman-33
View sourceMore from atman-33 →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Browser Extension Developer

Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.

281612 votes

Seo Optimizer

SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.

2132 votes

Google Official Seo Guide

Official Google SEO guide covering search optimization, best practices, Search Console, crawling, indexing, and improving website search visibility based on official Google documentation

1862 votes

Tanstack Start

Build a full-stack TanStack Start app on Cloudflare Workers from scratch — SSR, file-based routing, server functions, D1+Drizzle, better-auth, Tailwind v4+shadcn/ui. Use whenever the user mentions TanStack Start, asks to scaffold a full-stack Cloudflare app with SSR, wants an SSR dashboard, or asks for a React 19 + Cloudflare Workers app with file-based routing and server functions — even if they don't name TanStack Start specifically. No template repo — Claude generates every file fresh per ...

9881 votes

Pentest

PTES-aligned adversarial security audit for backend, frontend, and mobile applications. Produces a CVSS-scored Hacker Report with verified PoCs and phased remediation.

5491 votes
View all in development →