YouTrack Issue Tracker
Analysis
The skill is consistent with managing YouTrack, but it asks for a persistent YouTrack token and documents bulk issue changes through a referenced CLI helper that is not included in the artifacts.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
Use `ytctl` (in `scripts/`) for YouTrack issue tracking.
The provided manifest contains only SKILL.md and no install spec or scripts directory, so the CLI helper that would use the token and perform issue mutations is outside the reviewed artifacts.
ytctl bulk-update "project: SP state: Open" state "In Progress" ytctl bulk-comment "project: SP state: Open" "Batch update notice" ytctl bulk-assign "project: SP #unresolved" john.doe --dry-run
The documented CLI supports bulk modifications to all issues matching a query; this is purpose-aligned for workflow automation, but it can have broad impact if run without review.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Credentials stored in `~/.config/youtrack/config.json`:
{
"url": "https://your-instance.youtrack.cloud",
"token": "perm:xxx"
}
Or set env vars: `YOUTRACK_URL`, `YOUTRACK_TOKEN`The skill uses a personal YouTrack token, which is expected for the service integration but gives the CLI whatever permissions the token/user has.
