ms-teams-apps

Microsoft Teams bots and AI agents - Claude/OpenAI, Adaptive Cards, Graph API

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/ms-teams-apps/SKILL.md

Quality

Content

53%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 content is highly actionable with abundant executable code, but it is a long monolithic wall of inlined reference material with weak progressive disclosure and only loose validation guidance for risky operations. It would benefit from splitting reference material into bundle files and tightening verbose sections.

Suggestions

Split large reference blocks (Graph operations, Adaptive Card schemas, full bot templates, deployment recipes) into files under references/ and link to them one level deep, keeping SKILL.md a concise overview.

Trim redundant full implementations and explanatory ASCII boxes; assume Claude's knowledge of common concepts like OAuth and Adaptive Card structure to reduce token load.

Add explicit validation checkpoints and feedback loops (e.g., validate manifest before packaging, verify deployment endpoint after deploy) to the deployment and manifest workflows.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose, inlining multiple complete bot implementations, large manifest JSON, ASCII architecture boxes, and explanatory material Claude largely already knows; much of it could be trimmed or moved out.	2 / 5
Actionability	Provides copy-paste ready code and commands throughout (npm/npx CLI, full TypeScript samples, az CLI, Dockerfile, docker-compose, unit tests) covering the common build cases.	5 / 5
Workflow Clarity	Quick start, deployment, and testing sections are sequenced, but risky operations (manifest packaging, deployment) lack explicit validate-checkpoint feedback loops, which caps workflow clarity.	3 / 5
Progressive Disclosure	No bundle files exist and everything is inlined into a single monolithic SKILL.md; content that clearly belongs in separate reference files (Graph operations, full templates, deployment recipes) is buried rather than split out.	2 / 5
	Total	12 / 20 Passed

Description

78%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, clearly scoping a Microsoft Teams app-building skill with concrete integrations and an explicit when-to-use trigger. It is concise but slightly light on enumerated concrete actions and synonym coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Teams bots and AI agents) plus several concrete integrations (Claude/OpenAI, Adaptive Cards, Graph API), listing specific capabilities with only minor gaps in coverage.	4 / 5
Completeness	Answers 'what' in the description and supplies an explicit 'when' via the when-to-use field ('When building Microsoft Teams bots, tabs, or message extensions'), with the when clause concrete but slightly less granular than ideal.	4 / 5
Trigger Term Quality	Includes natural terms users would say ('Microsoft Teams bots', 'tabs', 'message extensions', 'AI agents') alongside specific technology keywords, though a few synonyms or file-extension variants are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clearly defined niche (Microsoft Teams apps) with specific triggers (bots, tabs, message extensions) and minimal overlap risk with unrelated skills.	5 / 5
	Total	17 / 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 (1253 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: alinaqi/claude-bootstrap
Path: skills/ms-teams-apps/SKILL.md
Commit: abc600e

Reviewed: 7 days 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.