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
Variable passing and escaping across jobs
isOutput=true present
100%
100%
Percent escaping
100%
100%
Newline escaping
0%
100%
Carriage return escaping
0%
100%
xtrace disabled around command
0%
100%
xtrace restored after command
0%
100%
##vso format correct
100%
100%
Cross-job reference syntax
100%
100%
Same-step unavailability
100%
100%
isOutput vs no-isOutput distinction
50%
100%
Failure signaling and task state control
task.logissue used for errors
0%
100%
task.complete result=Failed
100%
100%
Non-zero exit code
100%
100%
No contradictory signaling
100%
100%
##vso format correct
100%
100%
log-formatting vs agent-action distinction
100%
100%
##[error] vs task.logissue distinction
25%
100%
No contradictory signal explanation
100%
100%
Intent classification documented
100%
100%
Summary publishing and build metadata
Absolute path for uploadsummary
100%
100%
Run identifier in summary
100%
100%
Summary idempotency addressed
100%
100%
No colon in build tags
100%
100%
build.addbuildtag format correct
100%
100%
uploadsummary format correct
100%
100%
Log-formatting grouping used
100%
100%
Log-formatting vs agent-action distinction
100%
100%
Absolute path requirement explained
100%
100%
Uploadsummary points to .md file
100%
100%
b74de5e
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.