Standing context for Slack sibling agents — one room per team, creator-posted introductions, bot-to-bot hop discipline. Ships as instructions.md composed into the group's CLAUDE.md at spawn; there is no workflow to invoke.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add nanocoai/nanoclaw --skill slack-construct-agents --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Slack Construct Agents?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/nanocoai-slack-construct-agents)More formats (shields.io, HTML) on the badges page.
---
name: slack-construct-agents
description: Standing context for Slack sibling agents — one room per team, creator-posted introductions, bot-to-bot hop discipline. Ships as instructions.md composed into the group's CLAUDE.md at spawn; there is no workflow to invoke.
---
# Slack construct — sibling agents
This skill is a carrier for standing context, not an on-demand workflow. Its
payload is `instructions.md` in this directory: the rules an agent needs when
it shares Slack with sibling agents it can create (`create_agent`) and room
with (`create_room` / `add_to_room`) — team-room shape, who posts the
introduction, and the bot-to-bot self-limit.
The host composes every container skill's `instructions.md` into each group's
CLAUDE.md at spawn (`src/project-doc-compose.ts`), so if you are reading this
from inside a session, those rules are already part of your standing
instructions. There is nothing further to load or run here.
The room-and-canvas half of the Slack standing context (mention engagement,
canvas discipline, access rules) ships separately with the Slack channel
payload as the `slack-construct` skill; this fragment layers the
sibling-agent rules on top and arrives with the slack-agent-flow 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.
No comments yet. Be the first to comment!
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', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.