Google Model Armor: Create a new Model Armor template.
67
60%
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 ./skills/gws-modelarmor-create-template/SKILL.mdQuality
Discovery
32%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 very terse—it identifies the product (Google Model Armor) and a single action (create a template) but lacks a 'Use when' clause, detailed capabilities, and natural trigger terms. It would be difficult for Claude to reliably select this skill from a large pool because the description doesn't explain the context or scenarios that should trigger its use.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to create content safety or moderation templates in Google Cloud Model Armor.'
Include natural trigger terms and variations users might say, such as 'GCP Model Armor', 'content safety template', 'AI guardrails', 'moderation policy'.
Expand the capability description to list specific actions beyond just 'create', such as configuring safety filters, setting thresholds, or specifying blocked content categories.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Model Armor) and one action (create a new template), but does not list multiple concrete actions or elaborate on what creating a template involves. | 2 / 3 |
Completeness | States what it does (create a Model Armor template) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also minimal, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Google Model Armor' and 'template', but misses common variations or related terms users might say (e.g., 'content safety', 'guardrails', 'AI safety filter', 'GCP Model Armor'). | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Google Model Armor' is fairly specific to a particular GCP product, which helps distinguish it, but the generic 'template' term could overlap with other template-creation skills. More specificity about the type of template would reduce conflict risk. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise CLI skill that provides clear actionable guidance for creating a Model Armor template. Its main weakness is the lack of post-execution validation or error handling guidance for what is explicitly marked as a write command. The flag table, examples, and cross-references are all well done.
Suggestions
Add a validation/verification step after template creation (e.g., how to confirm the template was created successfully or how to handle common errors)
Consider adding a brief example of what a successful output looks like so Claude can verify the operation completed correctly
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section serves a purpose — usage, flags table, examples, tips, and cross-references. No unnecessary explanations of what Model Armor is or how GCP works. | 3 / 3 |
Actionability | Provides concrete, copy-paste-ready CLI commands with clear flag descriptions. The examples show both preset and JSON usage patterns, and the flags table specifies required vs optional with defaults. | 3 / 3 |
Workflow Clarity | This is a write/destructive command that correctly includes a caution to confirm with the user before executing. However, there's no validation step after creation (e.g., verify the template was created successfully, check for errors) and no error recovery guidance, which caps this at 2 for a write operation. | 2 / 3 |
Progressive Disclosure | Clear structure with well-signaled references to the shared skill for auth/global flags and to the parent modelarmor skill. Content is appropriately scoped to this single command with one-level-deep cross-references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
a3768d0
Table of Contents
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.