gws-modelarmor-create-template
Google Model Armor: Create a new Model Armor template.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill gws-modelarmor-create-template61
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
22%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 description is too terse and assumes familiarity with Google Model Armor. It fails to explain what Model Armor templates are used for, what creating one involves, and critically lacks any 'Use when...' guidance for skill selection. The Google product name provides some distinctiveness but the description needs substantial expansion.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Model Armor', 'content filtering', 'AI safety guardrails', 'Google Cloud security'
Explain what Model Armor templates do (e.g., 'configure content filtering rules, set safety thresholds, define blocked topics')
Include natural user phrases that would trigger this skill (e.g., 'set up content moderation', 'create safety filters for AI')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names one vague action ('Create a new Model Armor template') without explaining what Model Armor is, what templates contain, or what concrete capabilities this enables. | 1 / 3 |
Completeness | Only partially addresses 'what' (create a template) with no explanation of what that means. Completely missing 'when' guidance - no 'Use when...' clause or trigger conditions. | 1 / 3 |
Trigger Term Quality | Includes 'Google Model Armor' and 'template' which are relevant keywords, but lacks common variations or natural phrases users might say (e.g., 'security template', 'AI safety', 'content filtering', 'guardrails'). | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Model Armor' is a specific product name which helps distinctiveness, but 'template' is generic and could overlap with other template-creation skills without more context about the domain. | 2 / 3 |
Total | 6 / 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-crafted skill that efficiently documents a CLI command for creating Model Armor templates. It excels in conciseness and actionability with clear examples and flag documentation. The main weakness is the lack of explicit validation/verification steps for this write operation, which would help users confirm successful template creation.
Suggestions
Add a verification step showing how to confirm the template was created successfully (e.g., a follow-up list command or expected output)
Include error handling guidance for common failure scenarios (e.g., template already exists, invalid JSON format)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, presenting only essential information without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands with clear flag documentation. The examples show exact usage patterns with real flag combinations that can be executed immediately. | 3 / 3 |
Workflow Clarity | This is a single-command skill with clear usage, but for a write operation it lacks explicit validation steps. The caution note mentions confirming with user but doesn't specify how to verify the template was created successfully or handle errors. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear prerequisite reference, well-organized sections, and appropriate one-level-deep references to related skills. The See Also section provides clear navigation to related content. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 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.