dev-docs-guide

Search the public Glean developer documentation for API, SDK, MCP, authentication, indexing, and integration details. Use when the user is building with Glean rather than searching internal company knowledge — trigger phrases include Glean API, Glean SDK, integrate with Glean, indexing API, Glean Python or JavaScript SDK, and how to authenticate with Glean. Don't use it for internal company knowledge, which the using-glean skill covers.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

100%

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

A tight, well-structured routing skill for Glean Dev Docs MCP tools: actionable examples, a clear sequenced workflow with a review checkpoint, and clean section organization with no unnecessary references. Nothing is padded or explained that Claude would already know.

Dimension	Reasoning	Score
Conciseness	Lean ~45-line body with no concept padding (no explaining what Glean or MCP is); every section earns its place and assumes Claude's competence, matching the level-3 'lean and efficient' anchor.	3 / 3
Actionability	Provides concrete, copy-paste-ready tool invocations — `docs_search "API authentication"` and `docs_fetch "https://developers.glean.com/docs/api/auth"` — plus a Need/Tool/Example table and concrete good/bad query examples.	3 / 3
Workflow Clarity	Four-step sequence (Search → Review → Fetch → Cite) is clearly ordered with a 'Review results' checkpoint before fetching; this is a simple read-only workflow with no destructive/batch step, so no validation cap applies per the simple-skills note.	3 / 3
Progressive Disclosure	A self-contained sub-50-line skill with no bundle files and no nested references, organized into clearly labeled sections (Tools, When to use, Tool selection, Workflow, Query tips, Differentiating), which the rubric permits to score 3 for simple skills.	3 / 3
	Total	12 / 12 Passed

Description

100%

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, third-person description that states concrete capabilities, supplies natural trigger phrases, and explicitly differentiates from a sibling skill. It satisfies both the 'what' and 'when' requirements with no padding or over-claims.

Dimension	Reasoning	Score
Specificity	Enumerates concrete capability areas — 'API, SDK, MCP, authentication, indexing, and integration details' — tied to the concrete action 'Search the public Glean developer documentation', beating the vague single-action anchor at level 2.	3 / 3
Completeness	Clearly answers both what ('Search the public Glean developer documentation for...') and when ('Use when the user is building with Glean... — trigger phrases include...'), with explicit triggers satisfying the level-3 anchor.	3 / 3
Trigger Term Quality	Explicitly lists natural trigger phrases a developer would say — 'Glean API, Glean SDK, integrate with Glean, indexing API, Glean Python or JavaScript SDK, and how to authenticate with Glean' — giving broad, natural coverage.	3 / 3
Distinctiveness Conflict Risk	Carves a clear niche (public developer documentation) and explicitly disambiguates from the `using-glean` skill ('Don't use it for internal company knowledge, which the using-glean skill covers'), making mis-triggering unlikely.	3 / 3
	Total	12 / 12 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: gleanwork/claude-plugins
Commit: 00c3466

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.