ms365-tenant-manager
Comprehensive Microsoft 365 tenant administration skill for setup, configuration, user management, security policies, and organizational structure optimization for Global Administrators
Install with Tessl CLI
npx tessl i github:alirezarezvani/claude-code-skill-factory --skill ms365-tenant-manager41
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%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 identifies the domain and target audience (Global Administrators) but relies on high-level category terms rather than specific actions. The critical weakness is the complete absence of a 'Use when...' clause, making it unclear when Claude should select this skill over others. Adding explicit triggers and more concrete action examples would significantly improve skill selection accuracy.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about M365 admin tasks, tenant configuration, Azure AD user management, or Global Administrator duties'
Include common term variations users would naturally say: 'M365', 'Office 365', 'O365', 'Azure AD', 'admin center', 'license assignment'
Replace high-level categories with specific concrete actions: 'create and manage user accounts, assign licenses, configure conditional access policies, set up security groups'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Microsoft 365 tenant administration) and lists several action areas (setup, configuration, user management, security policies, organizational structure optimization), but these are high-level categories rather than concrete specific actions like 'create user accounts' or 'configure MFA policies'. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and since the 'when' is entirely absent, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'Microsoft 365', 'tenant administration', 'user management', 'security policies', and 'Global Administrators', but misses common variations users might say like 'M365', 'Office 365', 'Azure AD', 'admin center', or 'license management'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Microsoft 365 tenant administration' and 'Global Administrators' provides some specificity, but terms like 'user management' and 'security policies' could overlap with other IT administration or Azure-specific skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a Microsoft 365 administration overview document than an actionable skill file. It's extremely verbose, explaining concepts Claude already knows, while providing zero executable code despite claiming to offer 'ready-to-use scripts'. The content would benefit from dramatic reduction in explanatory text and addition of actual PowerShell/Graph API examples.
Suggestions
Replace abstract descriptions with actual executable PowerShell/Microsoft Graph code examples for common operations (e.g., user creation, Conditional Access policy setup)
Remove explanations of concepts Claude already knows (what MFA is, Zero Trust principles, basic PowerShell practices) - focus only on project-specific configurations
Add explicit validation checkpoints to workflows, especially for bulk operations and security policy changes (e.g., 'Run Get-MgUser to verify before proceeding')
Move detailed best practices, common tasks, and security considerations to separate reference files, keeping SKILL.md as a concise overview with quick-start examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanations of concepts Claude already knows (what MFA is, what Zero Trust means, basic PowerShell practices). Lists every possible feature and consideration rather than focusing on actionable guidance. Much of this content is general Microsoft 365 knowledge that doesn't need to be in a skill file. | 1 / 3 |
Actionability | Despite claiming to provide 'ready-to-use scripts' and 'step-by-step instructions', the content contains zero executable code examples. References scripts like 'tenant_setup.py' and 'user_management.py' without showing any actual code. All guidance is abstract descriptions rather than concrete, copy-paste ready commands. | 1 / 3 |
Workflow Clarity | Lists steps for common tasks (Initial Tenant Setup, User Onboarding, Security Hardening) but lacks explicit validation checkpoints and feedback loops. No verification steps between operations, no error recovery guidance, and no 'validate before proceeding' patterns for these potentially destructive administrative operations. | 2 / 3 |
Progressive Disclosure | References external scripts and resources but the main file is a monolithic wall of text covering everything from capabilities to limitations to resources. Content that should be in separate files (detailed best practices, common tasks, security considerations) is all inline. The structure exists but organization is poor. | 2 / 3 |
Total | 6 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.