mcpb-manifest

This skill should be used when the user asks to "configure manifest.json", "mcpb manifest spec", "manifest.json fields", "user_config in mcpb", "mcpb icon configuration", "set up manifest for desktop extension", "mcpb compatibility settings", "mcpb server types", "mcp_config variables", or needs detailed reference for the manifest.json file used in MCPB desktop extensions. Provides the complete field reference, user_config schema, server type examples, and variable substitution patterns.

Quality

84%

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

Quality

Content

72%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 strong, actionable field reference with copy-paste JSON for every server and config type, but it loads the entire reference into context rather than progressively disclosing it, and its validate guidance lacks a feedback loop.

Suggestions

Add a brief numbered workflow (draft fields → `mcpb validate manifest.json` → fix errors → re-validate → `mcpb pack`) with an explicit retry loop so the validation step is a real checkpoint.

Move the Full Example manifest.json and All Config Types Example into separate reference files (e.g. references/full-example.json, references/user-config-types.md) and link to them from a leaner overview, reducing the inlined ~389 lines.

Deduplicate the node server snippet and the manifest_version/name/version fields, which currently appear in both the Minimal manifest and the Required Fields table.

Dimension	Reasoning	Score
Conciseness	Mostly dense, useful tables and code with little concept-over-explanation, but the minimal manifest, Required Fields table, and Full Example repeat the same fields, and the node server snippet recurs across sections — minor trimming opportunities.	4 / 5
Actionability	Copy-paste-ready JSON examples cover node, python, uv, and binary servers, every user_config type, platform overrides, and a concrete `mcpb validate manifest.json` command, fully covering common cases.	5 / 5
Workflow Clarity	A 'Validate Your Manifest' checkpoint is present ('Always validate before packing'), but there is no explicit write→validate→pack sequence or feedback loop describing what to do on validation failure.	3 / 5
Progressive Disclosure	Internal structure is good (TOC, clear headers), but at ~389 lines all reference material is inlined in one file with no external references, when large field-reference/example sections could live in separate files.	3 / 5
	Total	15 / 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.

The description is exemplary: it pairs an explicit 'what' with a rich set of natural 'when' triggers and concrete deliverables, all in third person. Its only weakness is that the bare 'manifest.json' trigger could overlap with unrelated manifest-editing skills.

Dimension	Reasoning	Score
Specificity	Explicitly enumerates concrete deliverables — 'complete field reference, user_config schema, server type examples, and variable substitution patterns' — giving comprehensive coverage of what the skill provides rather than vague abstractions.	5 / 5
Completeness	Clearly answers both 'what' ('Provides the complete field reference, user_config schema...') and 'when' ('This skill should be used when the user asks to...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Quotes many natural trigger phrases users would say ('configure manifest.json', 'mcpb icon configuration', 'mcpb compatibility settings') with synonyms and the .json extension, matching comprehensive natural-term coverage.	5 / 5
Distinctiveness Conflict Risk	MCPB-qualified triggers carve a clear niche, but bare 'manifest.json' is a generic filename with minor overlap risk against other manifest-editing skills, so it sits just below the minimal-conflict anchor.	4 / 5
	Total	19 / 20 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
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	15 / 16 Passed

Repository: seanGSISG/claude-depot
Path: plugins/mcp-toolkit/skills/mcpb-manifest/SKILL.md
Commit: 48bf6a4

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