genkit-infra-expert
Execute use when deploying Genkit applications to production with Terraform. Trigger with phrases like "deploy genkit terraform", "provision genkit infrastructure", "firebase functions terraform", "cloud run deployment", or "genkit production infrastructure". Provisions Firebase Functions, Cloud Run services, GKE clusters, monitoring dashboards, and CI/CD for AI workflows.
57
50%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/devops/jeremy-genkit-terraform/skills/genkit-infra-expert/SKILL.mdQuality
Discovery
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.
This is a strong skill description that clearly defines its niche at the intersection of Genkit and Terraform deployment. It provides specific concrete actions, explicit trigger phrases, and clear when/what guidance. The only minor issue is the slightly awkward opening 'Execute use when' which could be smoother, but it doesn't materially impact functionality.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Provisions Firebase Functions, Cloud Run services, GKE clusters, monitoring dashboards, and CI/CD for AI workflows.' These are concrete, specific infrastructure components. | 3 / 3 |
Completeness | Clearly answers both what ('Provisions Firebase Functions, Cloud Run services, GKE clusters, monitoring dashboards, and CI/CD for AI workflows') and when ('use when deploying Genkit applications to production with Terraform') with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would say: 'deploy genkit terraform', 'provision genkit infrastructure', 'firebase functions terraform', 'cloud run deployment', 'genkit production infrastructure'. These cover multiple natural variations combining the key technologies. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining Genkit + Terraform + specific infrastructure targets (Firebase Functions, Cloud Run, GKE). Unlikely to conflict with generic Terraform or generic deployment skills due to the specific Genkit + Terraform intersection. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a hollow outline with no actionable content. It lists high-level steps without any concrete Terraform code, CLI commands, or specific configurations, and defers all meaningful content to reference files that don't exist in the bundle. The prerequisites section explains things Claude already knows, and the workflow lacks any validation checkpoints despite involving infrastructure deployment.
Suggestions
Add concrete, executable Terraform HCL snippets for at least one deployment target (e.g., Cloud Run) directly in the SKILL.md, including provider configuration, resource definitions, and Secret Manager integration.
Replace the vague 8-step workflow with specific commands and explicit validation checkpoints, e.g., 'terraform plan' review step before 'terraform apply', and a post-deployment curl command to verify Genkit flow endpoints.
Either create the referenced bundle files (implementation.md, errors.md, examples.md) with real content, or inline the essential information directly in the SKILL.md.
Remove the prerequisites section entirely—Claude knows what Terraform, gcloud, and Firebase CLI are—and replace it with a concise 'Required inputs' section listing only the specific variables/values needed from the user.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is padded with unnecessary content Claude already knows (prerequisites like 'install Terraform', 'authenticate gcloud'), explains obvious concepts, and the instructions are vague high-level steps that add little value. The prerequisites section and generic output section waste tokens without providing actionable information. | 1 / 3 |
Actionability | There is no concrete code, no executable Terraform configurations, no specific commands, and no copy-paste ready examples. The instructions are entirely abstract ('Choose Deployment Target', 'Configure Terraform Backend') with no actual HCL, CLI commands, or specific implementation details. Everything actionable is deferred to reference files that don't exist in the bundle. | 1 / 3 |
Workflow Clarity | The 8 steps are vague labels without any validation checkpoints, feedback loops, or error recovery guidance. For a skill involving infrastructure deployment (a destructive/risky operation), there are no explicit validation steps integrated into the workflow. 'Validate Deployment' is listed as a final step but provides no specifics on how to validate. | 1 / 3 |
Progressive Disclosure | The skill references multiple external files (implementation.md, errors.md, examples.md, genkit-examples/) but none of these files exist in the bundle. The main SKILL.md contains almost no substantive content itself, making it an empty shell that points to nonexistent resources. This is worse than a monolithic file because there's no content anywhere. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.