CtrlK
BlogDocsLog inGet started
Tessl Logo

teams-planner-task-management

Review and manage Microsoft Planner tasks from Teams workflows. Use when the user wants to inspect plans or buckets, create tasks from follow-ups, update task fields, or safely delete a Planner task.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

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 concise, well-structured instruction-only skill with a clear sequenced workflow and explicit safety checkpoints for destructive operations. The only gap is actionability: guidance is specific and operation-named but lacks any executable or copy-paste-ready artifacts.

Suggestions

Add one or two short, copy-paste-ready snippets or parameter signatures for the most common operations (e.g. an example `create_planner_task` invocation with its fields) to lift actionability to fully executable.

Include a brief inline example of a proposal payload (title, assignee, due date, target bucket) so the Output Conventions section doubles as a concrete template.

Clarify how a follow-up becomes a task by showing the extracted-action-item to task-field mapping rather than only describing it in prose.

DimensionReasoningScore

Conciseness

Lean and well-organized with no padding or explanation of concepts Claude already knows; every section and line earns its place.

3 / 3

Actionability

Concrete, operation-specific guidance names exact tools in backticks (e.g. `list_planner_tasks`, `update_planner_task`), but it is instruction-only with no executable code or copy-paste artifacts, so it is not fully copy-paste ready.

2 / 3

Workflow Clarity

Workflow is clearly sequenced with explicit safety/validation checkpoints for destructive and batch operations (resolve targets before delete/update, restate target, fetch current state first).

3 / 3

Progressive Disclosure

Single self-contained, well-organized SKILL.md under 50 lines with no need for external references; sections are clear and easy to navigate.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 concise, specific, and complete, naming concrete actions and an explicit 'Use when' trigger clause tied to natural Planner/Teams terminology. It is clearly distinguishable from other skills with minimal conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "inspect plans or buckets, create tasks from follow-ups, update task fields, or safely delete a Planner task" — matching the top anchor.

3 / 3

Completeness

Explicitly answers what ("Review and manage Microsoft Planner tasks") and when ("Use when the user wants to inspect plans or buckets, create tasks from follow-ups...").

3 / 3

Trigger Term Quality

Natural user phrasing is well covered: "Planner tasks", "plans", "buckets", "follow-ups", "Teams", "delete" — terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Niche is clearly Teams/Planner task management with distinct triggers, unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
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.