genkit-production-expert

Build production Firebase Genkit applications including RAG systems, multi-step flows, and tool calling for Node.js/Python/Go. Deploy to Firebase Functions or Cloud Run with AI monitoring. Use when asked to "create genkit flow" or "implement RAG". Trigger with relevant phrases based on skill purpose.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

57%

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

The content is well-structured with good progressive disclosure and a clear sequenced workflow, but it stays at an abstract directive level without inline executable code or explicit validation feedback loops. Actionability and workflow clarity are the main limiting factors.

Suggestions

Add at least one minimal executable code snippet in the Instructions (e.g., a complete ai.defineFlow() example with Zod schemas) so the body is copy-paste ready rather than deferring all code to references.

Insert an explicit validation checkpoint with a feedback loop before deployment (e.g., 'Run the flow in the Genkit Developer UI; if schema validation or safety errors occur, fix and re-run before deploying').

Tighten the Overview to avoid restating the description, and either reference or remove orphan bundle files (ARD.md, PRD.md, examples.md, scripts/init-genkit.sh) that are not navigated from the body.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining basics Claude knows, but the Overview restates the frontmatter description and several instruction steps are abstract directives ('Analyze the requirements to determine...') that could be tightened.	2 / 3
Actionability	Steps name concrete APIs (ai.defineFlow(), ai.defineTool(), ai.defineRetriever(), text-embedding-gecko) and a concrete error table, but the body contains no executable code blocks — implementation is deferred to references — matching the 'some concrete guidance but incomplete' anchor.	2 / 3
Workflow Clarity	Ten numbered steps give a clear sequence including 'Test locally ... then deploy', but there is no explicit validate-then-fix feedback loop before deployment, so checkpoints are implicit rather than enforced.	2 / 3
Progressive Disclosure	The body is an overview that points to one-level-deep, clearly signaled references (how-it-works.md, production-best-practices-applied.md, errors.md, workflow-examples.md), all of which exist as real files, matching the well-structured top anchor.	3 / 3
	Total	9 / 12 Passed

Description

85%

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 specific, complete, and distinctive, clearly stating capabilities and when to use the skill. Its weak spot is trigger-term breadth: only two narrow trigger phrases plus generic filler, so coverage of natural user phrasings is limited.

Suggestions

Replace 'Trigger with relevant phrases based on skill purpose' with concrete natural phrases users would say (e.g., 'genkit app', 'firebase ai flow', 'genkit deployment', 'add a tool to my genkit flow').

Add common variations of existing triggers such as 'build a genkit flow', 'set up RAG with genkit', or 'deploy genkit to cloud run'.

Trim the redundant restating of capabilities so the trigger list gets more emphasis within the description length budget.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Build production Firebase Genkit applications including RAG systems, multi-step flows, and tool calling' and 'Deploy to Firebase Functions or Cloud Run with AI monitoring' — matching the anchor for several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (build RAG/flows/tool-calling Genkit apps and deploy them) and when via a 'Use when...' clause with concrete triggers, satisfying the top anchor.	3 / 3
Trigger Term Quality	Includes some natural triggers ('Use when asked to "create genkit flow" or "implement RAG"') but coverage is thin and missing common variations, and the trailing 'Trigger with relevant phrases based on skill purpose' is generic filler rather than real keywords.	2 / 3
Distinctiveness Conflict Risk	The Firebase Genkit niche with Genkit/RAG-specific triggers is clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 2cafb23

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.