CtrlK
BlogDocsLog inGet started
Tessl Logo

migrate-slack-agents

Migrate a classic single-bot Slack install to one provisioned Slack app per existing agent group while preserving agent identities, workspaces, memory, and wiring behavior — or record the operator's choice to stay on classic, which remains supported. Use when /update-nanoclaw surfaces the Slack agents requirement, or standalone any time later.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

A dense, executable, well-sequenced migration runbook with strong validation gates and feedback loops. Its only soft spot is minor conciseness trimming and a lack of external reference structure (none needed).

DimensionReasoningScore

Conciseness

Largely lean and operational with no padding about concepts Claude already knows, but the ~290-line body has a few prose passages (invariants, rollback rationale) that could be tightened.

4 / 5

Actionability

Fully executable SQL queries and CLI commands with concrete flags (e.g. slack-agent-flow-finish.ts, ncl messaging-groups create, update-nanoclaw ack) cover the common cases copy-paste ready.

5 / 5

Workflow Clarity

Nine phases are explicitly sequenced with validation checkpoints (Phase 7 verify, Phase 8 cutover gate), explicit feedback loops ('If a test fails... repair and resume'), and a resume/partial-state model in Phase 9.

5 / 5

Progressive Disclosure

Well-organized into clearly headed phases with no nested references and no bundle files to disclose; the single-file structure is appropriate, though the length could in principle support a reference doc.

4 / 5

Total

18

/

20

Passed

Description

92%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.

A highly specific, complete, and distinctive description that names concrete actions and an explicit 'Use when' trigger. Slight room only in broadening natural-language trigger synonyms beyond internal command names.

DimensionReasoningScore

Specificity

Multiple concrete actions are named — migrate a classic single-bot Slack install to one provisioned app per agent group, preserve identities/workspaces/memory/wiring, or record a stay-on-classic choice — giving comprehensive coverage.

5 / 5

Completeness

It explicitly answers both 'what' (the migration and its preserves) and 'when' ('Use when /update-nanoclaw surfaces the Slack agents requirement, or standalone any time later').

5 / 5

Trigger Term Quality

Natural phrases like 'Migrate... Slack' and 'Slack agents' appear, and the command triggers /update-nanoclaw and /migrate-slack-agents are concrete, but coverage leans on internal command names rather than broad synonyms.

4 / 5

Distinctiveness Conflict Risk

The niche is sharply defined — classic single-bot Slack to per-group provisioned apps — with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 5 missing

Warning

Total

15

/

16

Passed

Repository
nanocoai/nanoclaw
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.