outlook-pre-onboarding-checklist-meeting

Create a 1-hour Outlook follow-up meeting for pre-onboarding after a successful Docusign workflow trigger, using the employee name and agreement effective date from workflow context.

Quality

72%

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 ./docs/special-ops/docusign-mcp/assets/sample-skill/SKILL.md

Quality

Content

78%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 a lean, well-structured, actionable single-purpose skill with clear sequencing and explicit error handling; its main weakness is mild redundancy between the Instructions and Rules sections.

Suggestions

Remove the redundant Rules that restate Instructions (no additional input, always use Employee Full Name/Effective Date, only after a successful trigger), or fold Rules into a single concise constraint list to tighten conciseness toward anchor 5.

Specify how to obtain 'the user's work hours' for the meeting start time (e.g., from a named calendar/profile field) and optionally show the Work IQ Calendar (Preview) tool call with its parameter mapping to push actionability to 5.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence with no over-explanation of known concepts, but the Rules section restates several Instructions (no additional input, use Employee Full Name/Effective Date, only after a successful trigger), which is minor padding that could be trimmed.	4 / 5
Actionability	Concrete, executable guidance names the exact tool, subject template, time zone, duration, and scheduling rule; code absence is not penalized for this instruction-only skill, but 'use the user's work hours for the meeting start time' is underspecified and no explicit tool-parameter mapping is given.	4 / 5
Workflow Clarity	Clear single-action sequence (confirm trigger, create meeting, send confirmation) with an explicit error-handling step; single meeting creation is not destructive/batch so the cap does not apply, but the error step reports rather than retries, so it is not a full validate-fix-retry loop.	4 / 5
Progressive Disclosure	A simple skill under 50 lines with well-organized Instructions and Rules sections and no need for external references, satisfying the simple-skill exception for a top score.	5 / 5
	Total	17 / 20 Passed

Description

66%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, distinct, and answers both what and when with a concrete conditional trigger, but it describes a single action and uses automation-oriented phrasing rather than rich natural trigger terms.

Suggestions

Add a 'Use when...' style trigger clause with natural user-facing phrasing (e.g., 'Use when scheduling a pre-onboarding follow-up after a signed agreement') to push completeness and trigger quality toward anchor 5.

Broaden trigger keywords with synonyms users might say (e.g., 'schedule', 'onboarding meeting', 'signed agreement') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Outlook meeting, pre-onboarding) and one concrete, well-specified action ('Create a 1-hour Outlook follow-up meeting... using the employee name and agreement effective date'), but does not list multiple actions, so it is not comprehensive.	3 / 5
Completeness	Clearly states both what (create a 1-hour Outlook follow-up meeting) and when (after a successful Docusign workflow trigger), but the single conditional trigger is not the multi-trigger-phrase comprehensive coverage of anchor 5.	4 / 5
Trigger Term Quality	Relevant domain keywords are present (Outlook, follow-up meeting, pre-onboarding, Docusign workflow trigger), but the phrasing is system-triggered rather than user-natural and lacks common variations or synonyms.	3 / 5
Distinctiveness Conflict Risk	A clear niche (Docusign pre-onboarding follow-up in Outlook) with a distinct trigger and minimal overlap risk with other skills.	5 / 5
	Total	15 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: microsoft/agent-academy
Path: docs/special-ops/docusign-mcp/assets/sample-skill/SKILL.md
Commit: 6300950

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