bootstrap
Meta-skill chaining /specify → /constitute → /plan → /tasks → spec-validation → dispatch-ready. Greenfield project from idea to…
Look up YouTrack issues by ID or list open issues. Use this skill FIRST whenever someone mentions an issue ID (CUBEOS-72, MESHSAT-27) or asks about project status, open issues, or issue details. This is for INFORMATION — not implementation. Do NOT escalate lookup requests.
$ npx -y skills add papadopouloskyriakos/agentic-chatops --skill youtrack-lookup --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/youtrack-lookupContext preview
The summary Claude sees to decide when to auto-load this skill.
Look up YouTrack issues by ID or list open issues. Use this skill FIRST whenever someone mentions an issue ID (CUBEOS-72, MESHSAT-27) or asks about project status, open issues, or issue details. This is for INFORMATION — not implementation. Do NOT escalate lookup requests.
name: youtrack-lookup
description: Look up YouTrack issues by ID or list open issues. Use this skill FIRST whenever someone mentions an issue ID (CUBEOS-72, MESHSAT-27) or asks about project status, open issues, or issue details. This is for INFORMATION — not implementation. Do NOT escalate lookup requests.
allowed-tools: Bash
user-invocable: true
metadata:
openclaw:
always: trueThis skill looks up issue information from YouTrack. Use it for ANY question about issues.
Step 1: Run the appropriate command using the Bash tool:
# Get issue details ./skills/yt-get-issue.sh CUBEOS-72 # List open issues ./skills/yt-list-issues.sh "project: CUBEOS State: Open" # List MeshSat issues (MeshSat = CUBEOS issues with "meshsat" in title) ./skills/yt-list-issues.sh "project: CUBEOS meshsat State: Open" # Get comments ./skills/yt-get-comments.sh CUBEOS-4
Step 2: Read the output and answer the user's question based on it.
1. **RUN THE TOOL FIRST.** Do NOT answer from memory. Do NOT say "not found in memory". Memory is stale — YouTrack is the source of truth. 2. **Do NOT escalate lookups.** Questions about issue status/details are YOUR job (Tier 1). Only escalate if the user asks to IMPLEMENT, BUILD, FIX, or REFACTOR something. 3. **Do NOT recommend the command to the user.** YOU run it yourself using the Bash tool.
./skills/yt-update-state.sh CUBEOS-4 "In Progress" ./skills/yt-post-comment.sh CUBEOS-4 "comment text" ./skills/yt-create-issue.sh CUBEOS "summary" "description"
AI agents that triage infrastructure alerts, investigate root causes, and propose fixes — while a solo operator sleeps. For the complete technical reference, see README.extensive.md.
Meta-skill chaining /specify → /constitute → /plan → /tasks → spec-validation → dispatch-ready. Greenfield project from idea to…
Phase C of greenfield project bootstrap. Produce constitution.md (5-15 non-negotiable articles) + steering/*.md (cross-cutting…
Phase D of greenfield project bootstrap. Produce design.md + data-model.md + contracts/{openapi,asyncapi,schemas/*} +…
Phase B of greenfield project bootstrap. Interview the operator to produce PROJECT.json + PROJECT.md + spec/NNN-*/requirements.md…
Phase E of greenfield project bootstrap. Atomize design.md + contracts into tasks.json with files_owned + dependencies +…
Query code graph database for function callers, callees, dependencies, and dead code in CubeOS and MeshSat repos.