CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

manage-idp

Manage Harness Internal Developer Portal (IDP) resources via MCP. Create service catalog templates, configure self-service environment provisioning workflows, generate service documentation, create Architecture Decision Records (ADRs), and design developer onboarding workflows. Use when asked to set up a service catalog, create self-service workflows, generate service docs, write ADRs, or onboard new developers. Do NOT use for service scorecards (use scorecard-review instead). Trigger phrases: service catalog, self-service, developer portal, IDP, onboarding workflow, ADR, architecture decision, service documentation, catalog template, developer experience, backstage.

Quality

83%

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

61%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 presents a clearly sequenced seven-step workflow with useful examples, performance notes, and troubleshooting, but most steps (4-7) lack the concrete MCP tool-call examples that Steps 1 and 3 provide, and the one template YAML is skeletal placeholder pseudocode. Validation guidance exists but lives in side notes rather than as explicit checkpoints in the step flow.

Suggestions

Add concrete harness_create/harness_update MCP parameter examples for the self-service provisioning, service documentation, ADR, and onboarding workflows — only Steps 1 and 3 currently include tool calls, leaving the majority of workflows as un-parameterized design bullets.

Replace the placeholder comments in the template YAML (e.g., "# Build, test, scan, push", "# Deploy to dev environment") with concrete stage specs, or move the full template to a reference file and inline a minimal working example.

Embed validation checkpoints directly into the step sequence (e.g., "verify the template renders in the catalog before publishing" after Step 3, "validate catalog-info.yaml against the Backstage entity schema before registering" after Step 5) instead of confining them to the Performance Notes section.

DimensionReasoningScore

Conciseness

The body is mostly efficient task-oriented lists, but Step 6 re-explains standard ADR structure ("Status (Proposed, Accepted, Deprecated, Superseded), Context, Decision, Consequences sections") that Claude already knows, and Step 2 re-enumerates the five workflows already stated in the intro and description. These are minor instances of over-explanation that could be trimmed, fitting the efficient-with-minor-trimming anchor.

4 / 5

Actionability

Only Steps 1 and 3 include concrete MCP tool calls with parameters; Steps 4-7 offer high-level design bullets ("Design the workflow with: Pre-approved infrastructure modules") with no tool invocations or parameter examples. The single template YAML also contains placeholder comments ("# Build, test, scan, push", "# Deploy to dev environment") rather than executable stage specs, fitting the incomplete-guidance/pseudocode anchor rather than the mostly-executable one.

3 / 5

Workflow Clarity

Steps 1-7 are clearly sequenced and labeled, and a Troubleshooting section covers three failure modes, but validation exists only as detached Performance Notes ("test end-to-end before publishing", "validate before registering") rather than explicit checkpoints embedded in the step flow. The sequence is present but checkpoints are implicit, matching that anchor rather than the most-checkpoints-present one.

3 / 5

Progressive Disclosure

No bundle files exist, and the ~158-line body is organized into clear sections (Instructions, Examples, Performance Notes, Troubleshooting). At this length the full template YAML and troubleshooting detail could arguably be split into reference files, but structure and placement are good with only minor organization gaps, fitting the good-structure anchor.

4 / 5

Total

14

/

20

Passed

Description

96%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.

A strong description that explicitly answers both what and when, enumerates five concrete actions, and provides an extensive trigger-phrase list plus a negative boundary for disambiguation. The only weakness is a few overly generic trigger phrases ("service documentation", "developer experience") that could pull the skill into conflicts with general documentation requests.

DimensionReasoningScore

Specificity

Lists five concrete actions ("Create service catalog templates, configure self-service environment provisioning workflows, generate service documentation, create Architecture Decision Records (ADRs), and design developer onboarding workflows") that comprehensively cover the skill's domain with no gaps, matching the comprehensive-coverage anchor rather than the minor-gaps anchor.

5 / 5

Completeness

Both what and when are explicit: the five actions state what the skill does, "Use when asked to set up a service catalog, create self-service workflows, generate service docs, write ADRs, or onboard new developers" states when, and a dedicated trigger-phrase list adds concrete triggers. The 'when' is fully explicit, so this exceeds the 4 anchor.

5 / 5

Trigger Term Quality

The explicit trigger list ("service catalog, self-service, developer portal, IDP, onboarding workflow, ADR, architecture decision, service documentation, catalog template, developer experience, backstage") covers eleven natural terms including synonyms; no file extensions are applicable to this non-file skill, so coverage is comprehensive.

5 / 5

Distinctiveness Conflict Risk

The niche is clear ("Manage Harness Internal Developer Portal (IDP) resources via MCP") with an explicit negative boundary ("Do NOT use for service scorecards (use scorecard-review instead)"), but generic trigger phrases like "service documentation" and "developer experience" create minor overlap risk with generic documentation/DX skills, fitting the mostly-distinct anchor better than the minimal-conflict anchor.

4 / 5

Total

19

/

20

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

Validation for skill structure

No warnings or errors.

Repository

harness/harness-ai

Path

plugins/claude/skills/manage-idp/SKILL.md

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.