add-teams

Add Microsoft Teams channel integration via Chat SDK.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/add-teams/SKILL.md

Quality

Content

77%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 highly actionable with a clearly sequenced, validated workflow and strong error-recovery guidance. Its main weaknesses are verbosity in the surrounding prose and a monolithic structure that doesn't split reference material into bundled files.

Suggestions

Tighten the recurring prose — the single-tenant 'right default for a self-hosted assistant' rationale and the global-vs-workspace CLI install justification are each stated more than once; state once and link.

Move the Manual Azure portal path and Optional configuration sections into reference files under references/ and link to them, so SKILL.md stays a lean overview and progressive disclosure improves.

Trim explanatory asides that restate what a directive already makes obvious (e.g. 'Re-runnable any time while signed in') to lift conciseness without losing the gotchas.

Dimension	Reasoning	Score
Conciseness	Mostly substantive domain/NanoClaw-specific gotchas rather than general concepts Claude already knows, but the prose around directives is noticeably verbose and repeats rationale (e.g. the single-tenant 'right default' explanation appears multiple times), fitting 'mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	Every step ships copy-paste-ready, fully executable commands — pinned dependency versions, exact curl/jq pipelines, env var pairing, and nc: directives with capture/validate flags — covering the common cases end to end.	5 / 5
Workflow Clarity	Steps are explicitly sequenced (Apply 1-4, Credentials sub-steps) with validation checkpoints (build guards the typed call, the registration test asserts the registry, login persistence is re-verified from a fresh process) and a dedicated Troubleshooting section providing feedback loops for error recovery.	5 / 5
Progressive Disclosure	No bundle files exist and the ~585-line document is monolithic; it is well-headed with internal anchor links, but long sections that could live in separate files (Manual Azure portal path, Troubleshooting, Optional configuration) are inlined, fitting 'some structure but content that should be separate is inline'.	3 / 5
	Total	16 / 20 Passed

Description

61%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 specific and distinctive about its Teams niche but is missing an explicit 'Use when...' trigger clause, which caps its completeness. Adding trigger phrases would round it out.

Suggestions

Add an explicit 'Use when ...' clause stating when Claude should invoke this skill (e.g. 'Use when adding Microsoft Teams as a chat channel or when the user mentions Teams integration').

Include a couple of natural trigger synonyms/variations (e.g. 'MS Teams', 'Teams bot') to broaden keyword coverage.

Optionally name one more concrete capability (e.g. 'register a bot and wire DMs') to lift specificity above a single action.

Dimension	Reasoning	Score
Specificity	Names the domain ('Microsoft Teams channel integration') and a concrete action plus method ('Add ... via Chat SDK') but covers only one action, matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	Has a clear 'what' (add Teams channel integration via Chat SDK) but no 'Use when...' or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural user terms ('Microsoft Teams', 'channel integration', 'Teams') with good coverage, but lacks synonyms/variations beyond the core phrase, fitting 'good keyword coverage; a few natural terms missing'.	4 / 5
Distinctiveness Conflict Risk	The Teams-specific niche is clear and unlikely to trigger for sibling channel skills, but the generic 'channel integration' pattern leaves minor overlap risk with other channel-add skills, fitting 'mostly distinct; minor overlap risk'.	4 / 5
	Total	14 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (585 lines); consider splitting into references/ and linking	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: nanocoai/nanoclaw
Path: .claude/skills/add-teams/SKILL.md
Commit: 7902716

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.