tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill google-cloud-agent-sdk-masterExecute automatic activation for all google cloud agent development kit (adk) Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
60%
Overall
Validation
Implementation
Activation
Validation
81%| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md line count is 53 (<= 500) | Pass |
frontmatter_valid | YAML frontmatter is valid | Pass |
name_field | 'name' field is valid: 'google-cloud-agent-sdk-master' | Pass |
description_field | 'description' field is valid (171 chars) | Pass |
description_voice | 'description' uses third person voice | Pass |
description_trigger_hint | Description includes an explicit trigger hint | Pass |
compatibility_field | 'compatibility' field not present (optional) | Pass |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
metadata_field | 'metadata' field not present (optional) | Pass |
license_field | 'license' field is present: MIT | Pass |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_present | SKILL.md body is present | Pass |
body_examples | Examples detected (code fence or 'Example' wording) | Pass |
body_output_format | Output/return/format terms detected | Pass |
body_steps | Step-by-step structure detected (ordered list) | Pass |
Total | 13 / 16 Passed |
Implementation
73%This skill is well-organized and concise, appropriately assuming Claude's competence with agent development concepts. However, it lacks concrete, executable examples - the instructions describe what to do at a high level without providing specific code scaffolds, commands, or copy-paste ready implementations that would make it immediately actionable.
Suggestions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of what ADK is or how agents work. Every section serves a purpose without padding or unnecessary context. | 3 / 3 |
Actionability | Instructions are clear but abstract - no concrete code examples, specific commands, or executable scaffolds are provided. The guidance describes what to do rather than showing how with copy-paste ready examples. | 2 / 3 |
Workflow Clarity | Steps are listed in a logical sequence (clarify → define → implement → validate), but validation checkpoints lack specificity. No concrete commands for smoke tests or deployment verification are provided. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections and appropriate references to external resources (full guide, docs, standards). Navigation is straightforward with one-level-deep references. | 3 / 3 |
Total | 10 / 12 Passed |
Activation
22%This description is severely deficient - it's essentially a template placeholder rather than a functional skill description. It names the technology (Google Cloud ADK) but fails to describe any concrete capabilities, and the trigger guidance is completely circular and unhelpful. Claude would have no meaningful basis for selecting this skill appropriately.
Suggestions
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - 'Execute automatic activation' is vague and abstract. It doesn't describe what the skill actually does with the Google Cloud ADK. | 1 / 3 |
Completeness | The 'what' is essentially missing (no actual capabilities described), and the 'when' is completely circular ('Use when appropriate context detected' provides no guidance). Both are very weak. | 1 / 3 |
Trigger Term Quality | Contains 'google cloud agent development kit (adk)' which is a relevant keyword, but 'appropriate context detected' and 'relevant phrases based on skill purpose' are circular and provide no actual trigger terms users would say. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'google cloud agent development kit (adk)' provides some specificity to a particular technology, but the lack of concrete actions means it could still conflict with other Google Cloud or development-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Reviewed
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.