azuredevops-pipelines-logging
Azure DevOps Pipelines logging-command guidance for reliable script-to-agent signaling, variable passing, and log UX. Use when writing or debugging `##vso[...]` and `##[...]` commands in YAML/Bash/PowerShell pipelines, troubleshooting output variable scope, handling secrets and masking behavior, or publishing summaries/artifacts from scripts. Pair with `azuredevops-pipelines-template` when template architecture and logging semantics are both in scope.
100
100%
Does it follow best practices?
Impact
100%
1.26xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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 an excellent skill description that hits all the marks. It provides specific concrete actions, uses natural technical terminology that users would actually search for, explicitly states when to use it, and even addresses potential skill conflicts by referencing a related skill. The description is appropriately detailed without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'script-to-agent signaling, variable passing, log UX', 'writing or debugging ##vso[...] and ##[...] commands', 'troubleshooting output variable scope', 'handling secrets and masking behavior', 'publishing summaries/artifacts from scripts'. | 3 / 3 |
Completeness | Clearly answers both what (logging-command guidance for signaling, variable passing, log UX) AND when with explicit 'Use when...' clause covering multiple trigger scenarios. Also includes helpful cross-reference to related skill. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Azure DevOps Pipelines', '##vso[...]', '##[...]', 'YAML/Bash/PowerShell pipelines', 'output variable scope', 'secrets', 'masking', 'artifacts', 'logging-command'. These are precise technical terms users would naturally use when seeking this help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific niche: Azure DevOps logging commands (##vso, ##[...]). The explicit differentiation from 'azuredevops-pipelines-template' skill shows awareness of potential overlap and provides clear guidance on when each applies. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that demonstrates excellent token efficiency while providing highly actionable guidance. The clear classification system (log-formatting vs agent-action), executable code examples with proper escaping, and well-structured progressive disclosure to reference files make this immediately useful. The pairing contract with the template skill shows thoughtful boundary definition.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context about what Azure DevOps is or how pipelines work generally. | 3 / 3 |
Actionability | Provides fully executable Bash code snippets for escaping, xtrace handling, and variable setting. The command formats are exact and copy-paste ready, with specific syntax patterns for different scopes. | 3 / 3 |
Workflow Clarity | Clear 6-step workflow with explicit verification step. The 'Fast Decision Rule' provides an unambiguous classification heuristic, and the Output Contract specifies exactly what responses should include with a verification checklist. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview and three clearly signaled one-level-deep references for detailed content. The 'Load on Demand' section explicitly tells when to load each reference file. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jjjermiah/dotagents
- Commit
b74de5e
- 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.