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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill genkit-infra-expertOverall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 applications and Terraform infrastructure provisioning. It provides excellent trigger term coverage with natural phrases users would say, lists specific infrastructure components it handles, and explicitly states when to use it. The description uses proper third-person voice throughout.
| 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') and when ('Execute use when deploying Genkit applications to production with Terraform' plus explicit trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'deploy genkit terraform', 'provision genkit infrastructure', 'firebase functions terraform', 'cloud run deployment', 'genkit production infrastructure'. These are phrases users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with the specific combination of Genkit + Terraform + production deployment. The trigger terms are specific enough (e.g., 'genkit terraform', 'firebase functions terraform') to avoid conflicts with generic deployment or Terraform skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
22%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 placeholder that describes what should be done without providing any concrete guidance on how to do it. It lacks executable Terraform code, specific commands, validation steps, and meaningful examples. The content defers everything to external references while the main body contains only abstract bullet points that Claude could generate without any skill file.
Suggestions
Add concrete Terraform code examples for at least one deployment target (e.g., Cloud Run) with actual resource definitions, variable declarations, and Secret Manager integration
Include specific gcloud/terraform commands for each step, such as 'terraform init -backend-config=bucket=...' and 'gcloud secrets create genkit-api-key --data-file=...'
Add validation checkpoints with specific commands like 'terraform plan' review, 'terraform apply' confirmation, and curl commands to test deployed Genkit flow endpoints
Provide at least one inline example showing the complete workflow from Terraform init to validated deployment, rather than deferring all examples to external files
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary padding like the verbose prerequisites list and generic instructions that don't add Genkit-specific value. The 'Output' section is empty, wasting space. | 2 / 3 |
Actionability | The skill provides only vague, high-level steps like 'Configure Terraform Backend' and 'Provision Compute' without any concrete code, commands, or Terraform configurations. No executable examples are provided - everything is abstract description. | 1 / 3 |
Workflow Clarity | While steps are numbered, they lack any validation checkpoints, feedback loops, or specific commands. For infrastructure deployment (a risky operation), there's no validation between steps, no rollback guidance, and 'Validate Deployment' is just 'test via HTTP endpoints' with no specifics. | 1 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) are present and one-level deep, but the main content is too thin - it defers almost everything to external files without providing a useful quick-start or any inline examples. The skill body itself is nearly empty of actionable content. | 2 / 3 |
Total | 6 / 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 — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
- 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.