Skills Guide

Tracker Validate

VerifiedSafe

Vendor-neutral wrapper that resolves the configured destination tracker and delegates to the matching vendor validator.

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

Recommended for

Claude CodeGit automationProduct managerBeginnerProductivitySolo / indie hacker

Automated summary

This skill acts as a vendor-neutral dispatcher that reads the project's tracker configuration and delegates validation to the matching validator (Jira, GitHub, or Linear).

Strengths

  • Resolves configuration with a local-then-global fallback using jq
  • Delegates to a vendor-specific validator without reimplementing gate logic
  • Passes the structured report through unchanged so callers can parse the gate lines
  • Clear error messages when the tracker is missing or unrecognized

Limitations

  • Strictly read-only, so it never fixes or creates any ticket
  • Depends on external validators (lisa-jira-validate-ticket, etc.) being installed
  • Assumes a .lisa.config.json in the expected format and that jq is available
When to use it

Use it to check whether a ticket or issue meets the required gates before creating or updating it, regardless of which tracker is configured.

When not to use it

Do not use it to write, edit, or create tickets, or when no tracker has been configured for the project yet.

Security analysis

Safe
Quality score72/100

The skill is a read-only dispatcher: it uses Bash only to read two config files via jq, then delegates to a vendor-specific validator skill and passes arguments through verbatim. It explicitly forbids writing to trackers and contains no destructive commands, network calls, obfuscated payloads, or secret handling. The only tool of note is Bash, used for a benign config lookup.

No concerns found

How this analysis is made

Examples

Validate a ticket in the configured tracker
/lisa:tracker:validate PROJ-482
Check an issue before creating it
/lisa:tracker:validate #231

name: lisa-tracker-validate description: "Vendor-neutral wrapper for the…" 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-mryiqgys/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-mryiqgys' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/tracker-validate-mryiqgys/download' --output '.skill-downloads/tracker-validate-mryiqgys/SKILL.md.part' && mv '.skill-downloads/tracker-validate-mryiqgys/SKILL.md.part' '.skill-downloads/tracker-validate-mryiqgys/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-mryiqgys/SKILL.md' && test -s '.skill-downloads/tracker-validate-mryiqgys/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/lisa-tracker-validate' && cp -R '.skill-downloads/tracker-validate-mryiqgys' '.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-mryiqgys'

openskills read 'tracker-validate-mryiqgys'

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-mryiqgys/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

PDF Reader

Productivity

Read and extract text from PDF files, including documents, reports, contracts, and spreadsheets. Works with local files, URLs, and WhatsApp attachments. Use whenever PDF content is needed, even if not explicitly requested.

Claude CodeCursorCodexbeginnerSafe 20,122
Skills Guide Bot

Discord Messaging Workflows

Productivity

Use the message tool to send, edit, and moderate Discord messages with interactive components.

Claude CodeintermediateSafe 388,021
Skills Guide Bot

Interactive Verdict Preview

Productivity

Generate an interactive HTML preview of keep/drop verdicts for maintainer review, then process the pasted feedback JSON.

Claude CodeintermediateSafe 316,798
Skills Guide Bot