argocd-app-deployer
Argocd App Deployer - Auto-activating skill for DevOps Advanced. Triggers on: argocd app deployer, argocd app deployer Part of the DevOps Advanced skill category.
34
0%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/02-devops-advanced/argocd-app-deployer/SKILL.mdQuality
Discovery
0%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 essentially a placeholder that restates the skill name and category without providing any useful information. It lacks concrete actions, natural trigger terms, explicit 'when to use' guidance, and any distinguishing details that would help Claude select it appropriately from a pool of skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates and configures ArgoCD Application manifests, syncs applications to Kubernetes clusters, manages deployment rollouts and rollbacks.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about deploying apps with ArgoCD, GitOps workflows, Kubernetes application syncing, or managing ArgoCD Application resources.'
Remove the duplicate trigger term and expand with natural variations users would say, such as 'ArgoCD', 'Argo CD', 'GitOps deploy', 'k8s app deployment', 'application manifest'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states the skill name and category ('DevOps Advanced') without describing what it actually does—no verbs like 'deploy', 'configure', 'sync', or 'manage' are present. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause and no description of capabilities beyond the skill name itself. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'argocd app deployer' repeated twice. It misses natural user phrases like 'deploy application', 'ArgoCD sync', 'Kubernetes deployment', 'GitOps', 'argo CD', or 'app of apps'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any DevOps or Kubernetes-related skill. Without specifying what ArgoCD app deploying entails, there is no clear niche or distinct trigger to differentiate it. | 1 / 3 |
Total | 4 / 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 an empty shell with no actual content. It contains only generic boilerplate descriptions of what the skill claims to do without any ArgoCD-specific instructions, commands, manifests, or workflows. It provides zero value beyond what Claude already knows and fails on every evaluation dimension.
Suggestions
Add concrete ArgoCD Application manifest examples (YAML) showing how to define an app, set sync policies, and configure health checks.
Include a step-by-step deployment workflow with explicit commands (e.g., `argocd app create`, `argocd app sync`, `argocd app get`) and validation checkpoints to verify successful deployment.
Provide specific configuration patterns for common scenarios like Helm-based apps, Kustomize overlays, and multi-environment setups with concrete, copy-paste-ready examples.
Remove all generic boilerplate sections (Purpose, When to Use, Example Triggers) and replace with actionable content that teaches ArgoCD app deployment patterns Claude wouldn't already know.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual knowledge or instructions that Claude doesn't already know. Every section is generic boilerplate. | 1 / 3 |
Actionability | There is zero concrete guidance—no commands, no code, no configuration examples, no ArgoCD manifests, no CLI usage. The content only describes what it could do rather than actually instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints. Claims to provide 'step-by-step guidance' but none is actually present. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic text with no references to detailed materials, no links to related files, and no meaningful structural organization beyond boilerplate headings. | 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
3e83543
- 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.