CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

slack-agent-flow

Let an existing Slack agent create new agents that arrive as their own Slack bots — provisioned app, operator DM, and a shared three-way room, hot-started without a host restart.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/slack-agent-flow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an exceptionally actionable, well-sequenced install runbook: every step is executable, validation is fail-fast and explicit, and failure recovery is documented with an idempotent retry script. Its weaknesses are a set of dangling references — REMOVE.md and the step-4 payload files are missing from the actual bundle — and a long inlined behavior section, which together hold progressive disclosure back. Conciseness is good, with only minor tightening opportunities.

Suggestions

Ship REMOVE.md in the bundle or drop the "(see REMOVE.md)" reference so the removal pointer resolves.

Verify the ~25 step-4 payload files actually ship alongside SKILL.md, or restructure so the copy block reflects the real bundle layout.

Move the detailed "How it behaves" bullets (install-gating, cache staleness, setup-wizard leg) into a one-level-deep reference file such as BEHAVIOR.md, keeping a short summary in SKILL.md.

DimensionReasoningScore

Conciseness

Dense and information-rich throughout — it assumes Claude's competence (never explains Slack, bots, dotenv, or build tooling) and every section carries non-obvious host-specific facts like the boot-warning semantics and the ≤30s a2a cache window. Not 5: a few passages could be tightened, notably the "Canonical home" paragraph and the long install-gating and setup-wizard bullets in "How it behaves"; not 3: there is no padding and no explanation of concepts Claude already knows.

4 / 5

Actionability

Fully executable end to end: copy-paste grep checks with exact patterns, nc:copy/nc:append blocks with explicit file lists and target paths, `pnpm run build`, exact vitest and container-run test commands, a restart command, and the finish-script invocation whose flags match the actual shipped script's usage. Not 4: the commands are complete and cover the common cases, including the failure/retry path, with no gaps requiring the reader to fill in steps.

5 / 5

Workflow Clarity

Steps 1–9 are clearly sequenced with explicit validation checkpoints (payload check, trunk-seam check with a fail-fast rationale, typed-call build guard, tests, restart) and documented feedback loops (re-apply skills or /update-nanoclaw on check failure, resumable failures with a named retry command, an idempotent finish script). The batch copy operations do have validation, so the destructive/batch cap does not apply; not 4 because checkpoints and error-recovery guidance are explicit at every stage rather than mostly present.

5 / 5

Progressive Disclosure

Section structure is clear (Prerequisites, Apply 1–9, How it behaves) and the one script reference (scripts/slack-agent-flow-finish.ts) is real and one level deep, but navigation is undermined by dangling references: "Removal (see REMOVE.md)" points at a file absent from the bundle, and the step-4 claim that the skill "ships its payload alongside this document" lists ~25 files (src/modules/slack-agent-flow/*, container/*) that are not present. The ~80-line inlined "How it behaves" section is also content that could live in a reference file. Not 4 because missing referenced files break the reference chain; not 2 because the sections are well organized with no nested-reference problem.

3 / 5

Total

17

/

20

Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concrete and highly specific about what the flow does, with natural trigger language for the Slack-agent niche. Its main weakness is the complete absence of a "when to use" trigger clause, which both caps completeness and leaves the description one notch short on trigger coverage. It is clearly distinguishable from generic skills, with only minor overlap risk against its own sibling skills.

Suggestions

Add an explicit trigger clause, e.g. "Use when a user asks an existing Slack agent to create, spawn, or add another agent/bot in Slack."

Mention the agent-facing room actions (create_room, add_to_room) and the create_agent parameter extensions so the description covers the full capability set.

Include one or two user-natural synonyms ("new Slack bot", "provision a bot") to broaden trigger matching.

DimensionReasoningScore

Specificity

Names several concrete actions — "create new agents that arrive as their own Slack bots", "provisioned app, operator DM, and a shared three-way room", "hot-started without a host restart" — matching the several-specific-actions anchor. Not 5 because coverage has gaps: the room actions (create_room / add_to_room) and the create_agent parameter extensions are part of the skill per the body but absent here, and "hot-started" is host-internal jargon rather than a user-visible capability; well above the 1–2-actions anchor.

4 / 5

Completeness

The "what" is clear and concrete (provisioned app, operator DM, shared three-way room, hot-start), but there is no "Use when..." clause or equivalent explicit trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. Not 4 because the "when" is entirely absent rather than merely imprecise; not 2 because the "what" is fully present.

3 / 5

Trigger Term Quality

Good keyword coverage with natural terms users would say — "Slack agent", "new agents", "Slack bots", "create" — squarely the good-coverage anchor. Not 5: missing common synonyms and variations ("new bot", "provision", "workspace") and no explicit use-when phrasing, while "hot-started" and "host restart" are internal jargon; better than the some-keywords-missing-synonyms anchor at 3.

4 / 5

Distinctiveness Conflict Risk

A clear niche — an existing Slack-wired agent spawning new agents as their own provisioned Slack bots — with distinct triggers, matching the mostly-distinct anchor. Not 5: within its own ecosystem it composes and overlaps with closely related skills (add-slack, slack-a2a-rooms) and the phrase "create new agents" could collide with a base agent-creation skill; far more distinct than the somewhat-specific anchor at 3.

4 / 5

Total

15

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

nanocoai/nanoclaw

Path

.claude/skills/slack-agent-flow/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.