Name: microsoft-365-people
Rating: 56.8 (1 reviews)
Author: membranedev

microsoft-365-people

Microsoft 365 People integration. Manage data, records, and automate workflows. Use when the user wants to interact with Microsoft 365 People data.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/microsoft-365-people/SKILL.md

Quality

Content

67%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 actionable and well-structured with a strong connection-state workflow, but it carries some concept explanation and filler that could be tightened, and the step numbering has a small inconsistency.

Suggestions

Trim the opening descriptive paragraph and remove filler lines like "Use action names and parameters as needed" to improve token efficiency.

Fix the step numbering so "1b" aligns with an explicit "1a/Step 1" and clarify where "Step 2" begins in the connection flow.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete CLI commands, but the opening paragraph explains what Microsoft 365 People is and filler like "Use action names and parameters as needed" could be trimmed.	3 / 5
Actionability	Provides copy-paste ready commands for install, login, connection ensure, action list/run, and proxy requests with a flags table; minor gaps remain around the empty-URL example and CONNECTION_ID placeholders.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-retry feedback loop, though the "Step 2" reference and 1b numbering introduce a minor sequencing ambiguity.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with no nested references and a self-contained structure; no bundle files exist, and the inline proxy/state reference is compact enough to stay in SKILL.md.	4 / 5
	Total	15 / 20 Passed

Description

62%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 covers the what and when at a basic level and names a clear niche, but its action verbs are generic and it lacks the concrete trigger synonyms (contacts, org chart, colleagues) that would make it surface reliably.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete capabilities such as "search colleagues, view contact details, explore org charts and reporting lines".

Expand the trigger clause to include natural synonyms users say, e.g. "Use when the user wants to look up contacts, colleagues, org charts, or reporting relationships in Microsoft 365 People".

Dimension	Reasoning	Score
Specificity	Names the domain ("Microsoft 365 People") and a couple of action phrases ("Manage data, records, and automate workflows"), but those actions are generic rather than concrete capabilities like "view org charts" or "search contacts".	3 / 5
Completeness	Answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Microsoft 365 People data"), but the trigger clause is generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes the core term "Microsoft 365 People" and "Microsoft 365 People data", but omits natural synonyms a user would say such as "contacts", "colleagues", or "org chart".	3 / 5
Distinctiveness Conflict Risk	The "Microsoft 365 People" niche is clearly distinct, with only minor overlap risk against related Microsoft 365 skills (Mail, Calendar, Files).	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/microsoft-365-people/SKILL.md
Commit: f484c82

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