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.
Install with Tessl CLI
npx tessl i github:jjjermiah/dotagents --skill azuredevops-pipelines-logging100
Does it follow best practices?
Validation for skill structure
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 demonstrates best practices. It provides specific concrete actions, uses natural technical trigger terms that users would actually search for, explicitly states both what the skill does and when to use it, and clearly distinguishes itself from related skills through precise scoping and cross-referencing.
| 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 reliable script-to-agent signaling, variable passing, and log UX') and when ('Use when writing or debugging ##vso[...] commands...') with explicit trigger scenarios. Also includes helpful pairing guidance with related skill. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: '##vso[...]', '##[...]', 'YAML/Bash/PowerShell pipelines', 'output variable scope', 'secrets', 'masking', 'summaries', 'artifacts', 'logging-command'. These are precise technical terms users would naturally use when seeking this help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche focus on Azure DevOps logging commands specifically. The explicit mention of '##vso[...]' and '##[...]' syntax, plus the pairing note distinguishing it from template architecture concerns, makes it unlikely to conflict with other skills. | 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 a high-quality skill that demonstrates excellent structure and actionability. It efficiently covers the domain with executable code examples, clear decision frameworks (log-formatting vs agent-action), and appropriate progressive disclosure to reference files. 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 syntax formats are exact and copy-paste ready, with specific property names and usage patterns. | 3 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced with explicit verification step. The 'Fast Decision Rule' and classification-first approach provide clear decision checkpoints. Failure semantics section addresses error handling explicitly. | 3 / 3 |
Progressive Disclosure | Excellent structure with clear overview in main file and well-signaled one-level-deep references to three specific reference files. Each reference file has explicit load conditions ('Load when...') making navigation intuitive. | 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.
- 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.