ff-oce-dashboard

Generate the OCE shift status dashboard. Triggers on: 'generate shift dashboard', 'show dashboard', 'shift status', 'status dashboard', 'what's going on', or any request for a NON-SPECIFIC overview of current OCE status (incidents, pipelines, errors).

Quality

95%

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

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary instruction skill: tightly scoped, fully actionable with exact tool calls and identifiers, and a clear multi-step workflow with validation checkpoints and error-recovery fallbacks. No bundle files are needed given the self-contained procedure.

Dimension	Reasoning	Score
Conciseness	The body is lean and operational — it never explains what IcM/ADO/Kusto/Teams are, and assumes Claude's competence; explanatory asides (e.g., why the `expand` parameter is required, why `ado-office` not `ado`) are justified operational knowledge Claude lacks, so every token earns its place per the level-3 anchor.	3 / 3
Actionability	Guidance is fully concrete and copy-paste ready: exact tool names, team IDs (98481, 149377, 98313), pipeline definition IDs (12, 56, 63, 29163), full parameter objects, an executable KQL query, and exact Teams teamId/channelId, matching the level-3 anchor.	3 / 3
Workflow Clarity	Steps are explicitly sequenced (Step 0 confirm → Step 1 launch → Step 2 collect → Step 3 present) with validation checkpoints: a user confirmation gate, a hard 90s timeout cutoff with explicit unavailable-handling, a Kusto fallback query, and a 'always terminate / FAILED: <reason>' contract for agents — matching the level-3 clear-sequence-with-feedback-loops anchor.	3 / 3
Progressive Disclosure	A single self-contained SKILL.md with no bundle files; content is well-organized into clearly labeled sections (Steps 0–3, Agents 1–6) with no nested references and nothing that should be split out, satisfying the well-organized-sections bar for a self-contained procedural skill.	3 / 3
	Total	12 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person voice, explicit trigger phrases, and a clear niche. Its only weakness is specificity — it describes one consolidated action rather than enumerating multiple distinct capabilities.

Suggestions

Optionally enumerate the constituent capabilities the dashboard aggregates (e.g., '...consolidating IcM incidents, pipeline health, error rates, and Teams alerts into one view') to lift specificity from a single action to multiple concrete actions.

Consider adding '.md' or 'report' as an additional natural trigger variant for users who ask for a written status report rather than a console dashboard.

Dimension	Reasoning	Score
Specificity	The phrase 'Generate the OCE shift status dashboard' names a concrete action and domain, but it is essentially a single consolidated action rather than the 'multiple specific concrete actions' the level-3 anchor requires; not a level-1 vague abstraction like 'Helps with documents'.	2 / 3
Completeness	It explicitly answers both 'what' ('Generate the OCE shift status dashboard') and 'when' ('Triggers on: ...') with explicit trigger guidance, matching the level-3 anchor; not level-2 since the 'when' is explicit rather than implied.	3 / 3
Trigger Term Quality	It lists natural phrases a user would say — 'generate shift dashboard', 'show dashboard', 'shift status', 'status dashboard', 'what's going on' — giving good coverage of common variations, matching the level-3 anchor.	3 / 3
Distinctiveness Conflict Risk	'OCE shift status dashboard' is a clear niche with distinct triggers, and the 'NON-SPECIFIC overview' qualifier helps avoid firing for specific single-service queries, matching the level-3 clear-niche anchor.	3 / 3
	Total	11 / 12 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: microsoft/FluidFramework
Path: .agency/plugins/ff-oce/skills/ff-oce-dashboard/SKILL.md
Commit: f9f2007

Reviewed: about 8 hours 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.