Skills Guide

Tracker Validate

VerifiedSafe

Vendor-neutral wrapper for the pre-write quality gate. Dispatches to the appropriate tracker validator (Jira, GitHub, or Linear) based on configuration. Read-only. Returns structured PASS/FAIL.

Download and use
Sby Skills Guide Bot
DevOpsIntermediate
7/22/2026
Claude Code
#tracker#validation#jira#github#linear

Recommended for

Backend developerClaude CodeDevOps engineerGit automation

Automated summary

This skill is a thin dispatcher that reads the tracker configured in .lisa.config.json and delegates pre-write validation to the matching vendor validator (Jira, GitHub, or Linear), staying read-only.

Strengths

  • Two-tier config resolution (local then global) via jq, consistent with lisa-tracker-write
  • Strict delegation to specialized validators without reimplementing gate logic
  • Structured PASS/FAIL output passed through unchanged for reliable parsing by callers
  • Guaranteed read-only: never writes to any tracker

Limitations

  • Only works when a tracker is configured; otherwise it halts with an error message
  • Supports only jira, github, and linear
  • Performs no validation itself: quality depends entirely on the invoked validator
When to use it

Use it when a workflow needs to check ticket or issue compliance before writing, or during post-write checks, regardless of the configured tracker.

When not to use it

Do not use it to create, edit, or close tickets, nor for trackers other than Jira, GitHub, or Linear.

Security analysis

Safe
Quality score80/100

The skill is a read-only dispatcher: it runs two local `jq` reads against .lisa.config.json/.local.json to resolve a tracker name, then delegates to a vendor validator skill with the arguments passed verbatim. There are no destructive commands, no network calls, no secret exfiltration, no obfuscated payloads, and no attempts to disable safety controls. Bash usage is limited to config parsing and is explicitly constrained by the stated read-only rule.

No concerns found

How this analysis is made

Examples

Pre-write gate check
/lisa-tracker-validate Validate the draft ticket before we write it: PROJ-412 add retry logic to the sync worker
Post-write verification
/lisa-tracker-validate Run the post-write checks on issue #238 and report PASS/FAIL per gate
Dry-run validation
/lisa-tracker-validate --dry-run new feature: export audit logs to S3

name: lisa-tracker-validate description: "Vendor-neutral wrapper for the pre-write quality gate. Reads the required tracker from .lisa.config.json and dispatches to lisa-jira-validate-ticket, lisa-github-validate-issue, or lisa-linear-validate-issue. Read-only — never writes to any tracker. Used by tracker-write Phase 5.5 (pre-write gate), tracker-verify (post-write checks), and the *-to-tracker dry-run paths. Output is structured PASS/FAIL per gate so callers can parse it." allowed-tools: ["Skill", "Bash", "Read"]

Tracker Validate: $ARGUMENTS

Thin dispatcher. Resolves the configured destination tracker and delegates to the matching vendor validator.

See the config-resolution rule for the full configuration schema and skill-mapping table.

Workflow

  1. Resolve tracker config (same logic as lisa-tracker-write Step 1):

    local_tracker=$(jq -r '.tracker // empty' .lisa.config.local.json 2>/dev/null)
global_tracker=$(jq -r '.tracker // empty' .lisa.config.json 2>/dev/null)
tracker="${local_tracker:-$global_tracker}"

  2. Dispatch

    • Missing / empty → stop and report "No tracker configured in .lisa.config.json. Run /lisa:setup:jira, /lisa:setup:github, or /lisa:setup:linear first."
    • jira → invoke lisa-jira-validate-ticket with $ARGUMENTS verbatim.
    • github → invoke lisa-github-validate-issue with $ARGUMENTS verbatim.
    • linear → invoke lisa-linear-validate-issue with $ARGUMENTS verbatim.
    • Anything else → stop and report "Unknown tracker '<value>' in .lisa.config.json. Expected 'jira', 'github', or 'linear'."

  3. Pass through the validator's structured report unchanged. Callers (e.g. lisa-jira-write-ticket Phase 5.5) parse the gate lines; do not paraphrase.

Rules

  • Read-only — never write to any tracker.
  • Never re-implement gate logic here. The gate definitions are the vendor validator's responsibility.
  • Never silently transform the input — pass $ARGUMENTS through verbatim.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/tracker-validate-mrwakbqy/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/tracker-validate-mrwakbqy' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/tracker-validate-mrwakbqy/download' --output '.skill-downloads/tracker-validate-mrwakbqy/SKILL.md.part' && mv '.skill-downloads/tracker-validate-mrwakbqy/SKILL.md.part' '.skill-downloads/tracker-validate-mrwakbqy/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/tracker-validate-mrwakbqy/SKILL.md' && test -s '.skill-downloads/tracker-validate-mrwakbqy/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/lisa-tracker-validate' && cp -R '.skill-downloads/tracker-validate-mrwakbqy' '.claude/skills/lisa-tracker-validate'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/tracker-validate-mrwakbqy'

openskills read 'tracker-validate-mrwakbqy'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/tracker-validate-mrwakbqy/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

Configure a Chat Channel with SecretRefs

DevOps

Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.

Claude CodeCodexintermediateSafe 387,940
Skills Guide Bot

Investigate ClickHouse CI Failures

DevOps

Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.

Claude CodeadvancedSafe 49,516
Skills Guide Bot

Ansible PR Review

DevOps

Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.

Claude CodeintermediateSafe 70,491
Skills Guide Bot