OpenLogi Device Diagnosis
AprilNEA/OpenLogi
Finds the first failing layer when an OpenLogi Logitech device is missing or misbehaving across enumeration, open, probe, IPC and UI.
Triage, debug, fix, and document issues for the Static Web Server (SWS) project — bug reports, root cause analysis, fix implementation, and regression prevention
Install Issue Tracking
$ npx skills add static-web-server/static-web-server --skill issue-tracking -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install static-web-server/static-web-server issue-tracking --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/static-web-server/static-web-server.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/issue-tracking .claude/skills/issue-tracking && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "issue-tracking" agent skill from https://github.com/static-web-server/static-web-server/tree/master/.agents/skills/issue-tracking into .claude/skills/issue-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-tracking", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/static-web-server/static-web-server/tree/master/.agents/skills/issue-trackingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add static-web-server/static-web-server --skill issue-tracking -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install static-web-server/static-web-server issue-tracking --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/static-web-server/static-web-server.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/issue-tracking .agents/skills/issue-tracking && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "issue-tracking" agent skill from https://github.com/static-web-server/static-web-server/tree/master/.agents/skills/issue-tracking into .agents/skills/issue-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-tracking", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add static-web-server/static-web-server --skill issue-tracking -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install static-web-server/static-web-server issue-tracking --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/static-web-server/static-web-server.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/issue-tracking .cursor/skills/issue-tracking && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "issue-tracking" agent skill from https://github.com/static-web-server/static-web-server/tree/master/.agents/skills/issue-tracking into .cursor/skills/issue-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-tracking", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/static-web-server/static-web-server.git --path .agents/skills/issue-tracking--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add static-web-server/static-web-server --skill issue-tracking -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install static-web-server/static-web-server issue-tracking --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/static-web-server/static-web-server.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/issue-tracking .gemini/skills/issue-tracking && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "issue-tracking" agent skill from https://github.com/static-web-server/static-web-server/tree/master/.agents/skills/issue-tracking into .gemini/skills/issue-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-tracking", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install static-web-server/static-web-server issue-trackingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add static-web-server/static-web-server --skill issue-tracking -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/static-web-server/static-web-server.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/issue-tracking .github/skills/issue-tracking && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "issue-tracking" agent skill from https://github.com/static-web-server/static-web-server/tree/master/.agents/skills/issue-tracking into .github/skills/issue-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-tracking", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add static-web-server/static-web-server --skill issue-tracking -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install static-web-server/static-web-server issue-tracking --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/static-web-server/static-web-server.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/issue-tracking .opencode/skills/issue-tracking && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "issue-tracking" agent skill from https://github.com/static-web-server/static-web-server/tree/master/.agents/skills/issue-tracking into .opencode/skills/issue-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-tracking", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
issue-tracking- GitHub stars
- 2.4k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 724 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Triage, debug, fix, and document issues for the Static Web Server (SWS) project — bug reports, root cause analysis, fix implementation, and regression prevention
- Works in 5 steps: Gather evidence: Logs (-g trace), stack… → Form a hypothesis: Based on the… → Test the hypothesis: Add tracing, run… → …
- Tasks that involve Task management
- SKILL.md covers Issue Triage, Root Cause Analysis, Fix Implementation and Regression Prevention, plus 2 more sections
- Calls curl and openssl
What it does
Issue Tracking is an agent skill from static-web-server/static-web-server. Triage, debug, fix, and document issues for the Static Web Server (SWS) project — bug reports, root cause analysis, fix implementation, and regression prevention
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Task management, Root cause analysis and QA and bug reports. It works with Rust and Linux. The repository describes itself as: A cross-platform, high-performance and asynchronous web server for static files-serving. ⚡. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Task management
- Tasks that involve Root cause analysis
- Tasks that involve QA and bug reports
Example prompts
- “/issue-tracking”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Gather evidence: Logs (-g trace), stack traces, HTTP response headers, request URIs, config file
- Form a hypothesis: Based on the evidence, propose what might cause the bug
- Test the hypothesis: Add tracing, run reproduction, or step through with a debugger
- Identify the root cause: Find the exact line or condition that triggers the bug. Don't stop at symptoms
- Verify the fix: The reproduction test now passes. The original scenario works
What it can do on your machine
Read from SKILL.md and the folder at commit 32ec4aa. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
curlopenssl
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Issue Tracking loads about 1.5k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 724 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from static-web-server/static-web-server at commit 32ec4aa, republished under its Apache-2.0 licence (© static-web-server). 724 words, ~1,467 tokens.
Download SKILL.mdSave it as
.claude/skills/issue-tracking/SKILL.md (or your agent's skills folder).- name
- issue-tracking
- description
- Triage, debug, fix, and document issues for the Static Web Server (SWS) project — bug reports, root cause analysis, fix implementation, and regression prevention
Issue Tracking & Debugging
Load this skill when triaging bug reports, investigating issues, implementing fixes, or writing post-mortem documentation for SWS.
When to load: triaging a new issue report, investigating a regression, writing a fix for a bug, drafting a post-mortem, or reviewing a bug-fix PR.
Issue Triage
Reproducibility First
- Can you reproduce it? Follow the exact steps in the report. If unreproducible, ask the reporter for environment details (OS, architecture, SWS version, config file, TLS setup)
- Minimal reproduction: Reduce the scenario to the smallest config + file structure that triggers the bug. Strip unrelated features
- Write a failing test first: Before fixing, write a test that reproduces the bug. Use the fixture infrastructure in
tests/andsrc/testing.rs
Severity Classification
| Severity | Definition | Response |
|---|---|---|
| P0 - Critical | Security vulnerability, data exposure, path traversal | Drop everything. Fix immediately. Security release |
| P1 - High | Broken core feature (file serving, TLS), crash on start | Fix in current sprint. Patch release |
| P2 - Medium | Broken non-core feature, workaround exists | Schedule in next sprint |
| P3 - Low | Cosmetic, log message, doc typo | Backlog. Fix when touching related code |
Root Cause Analysis
Debugging Process
- Gather evidence: Logs (
-g trace), stack traces, HTTP response headers, request URIs, config file - Form a hypothesis: Based on the evidence, propose what might cause the bug
- Test the hypothesis: Add tracing, run reproduction, or step through with a debugger
- Identify the root cause: Find the exact line or condition that triggers the bug. Don't stop at symptoms
- Verify the fix: The reproduction test now passes. The original scenario works
Rust Debugging
- Use
tracingcrate for structured logs: SWS usestracing-subscriber. Run with-g tracefor maximum detail. Log levels: ERROR (actionable), WARN (unexpected but handled), INFO (key events), DEBUG (detailed), TRACE (noisy) - Use
dbg!()for quick inspection: Temporary, remove before committing - Enable backtraces:
RUST_BACKTRACE=1for panic backtraces,RUST_LIB_BACKTRACE=1for error backtraces
HTTP Debugging
- Inspect response headers: Use
curl -v http://localhost:8787/pathto see full request/response exchange - Test with specific Accept-Encoding headers:
curl -H "Accept-Encoding: br" ...to test compression variant selection - Check security headers:
curl -I http://localhost:8787/ | grep -i 'x-\|strict\|csp\|referrer' - Test byte-range requests:
curl -H "Range: bytes=0-99" http://localhost:8787/file - CORS preflight debugging:
curl -X OPTIONS -H "Origin: https://example.com" -H "Access-Control-Request-Method: GET" http://localhost:8787/ - TLS verification:
openssl s_client -connect localhost:8787 -servername localhost
File-Serving Debugging
- Path resolution issues: Check if the file exists at the resolved path. SWS logs the resolved path at
tracelevel - Hidden file / symlink blocking: Verify
--include-hiddenand--follow-symlinkssettings (both default tofalse). Hidden files return 404 (stealth), symlinks return 403 - Index file resolution: If a directory returns 404 instead of an index, check
--index-fileslist and file existence - MIME type issues: SWS uses
mime_guessfrom file extension. If the wrongContent-Typeis served, check the file extension
Show full SKILL.md (270 more words)Show less
Fix Implementation
Before Writing the Fix
- Is there a failing test that reproduces the bug?
- Is the root cause identified (not just the symptom)?
- Does the fix address the root cause?
- Are there other places in the codebase with the same bug pattern?
Writing the Fix
- Minimal change: Fix the bug with the smallest possible code change. Do not refactor unrelated code in the same PR
- Add a regression test: The reproduction test becomes a permanent regression test
- Update documentation: If the fix changes behavior, update the relevant feature doc in
docs/content/features/
Commit Message Format
fix(scope): brief description of the fix
Detailed explanation of the root cause and the fix.
Include steps to reproduce, expected behavior, and actual behavior.
Fixes #123scope is the affected module or feature (e.g., compression, tls, static-files). See COMMITS.md for the full convention.
Regression Prevention
- The reproduction test stays: Every bug fix adds a test that prevents the same bug from returning
- Check similar code paths: Search the codebase for patterns that could cause the same class of bug
- Add a lint rule if applicable: If a pattern caused the bug and can be detected statically, add a clippy or ESLint rule
Post-Mortem (P0/P1 only)
For critical and high-severity issues, write a brief post-mortem:
- What happened: Timeline of the incident
- Root cause: The specific code or configuration that caused it
- Impact: What users were affected and how
- Fix: What change resolved the issue
- Prevention: What process, tooling, or test prevents recurrence
Store post-mortems in docs/post-mortems/YYYY-MM-DD-title.md.
Checklist
- Bug is reproduced and understood
- Root cause identified (not just symptom)
- Failing test written before the fix
- Fix is minimal and addresses root cause
- Regression test added
- Similar code paths checked for the same bug pattern
- Commit message follows format
© static-web-server, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/issue-tracking of static-web-server/static-web-server.
Open the folder on GitHubat commit 32ec4aa
Compare with similar skills
Issue Tracking next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Issue Tracking this skillstatic-web-server/static-web-server | 2.4k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| OpenLogi Device DiagnosisAprilNEA/OpenLogi | 23k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| OpenLogi macOS Permissions TriageAprilNEA/OpenLogi | 23k | — | ~2.5k | Automated safety check: Notes | Apache-2.0 | |
| The Art of Debuggingstas00/the-art-of-debugging | 1.7k | — | ~6.1k | Automated safety check: Notes | CC-BY-SA-4.0 | |
| Debuggnomeria/usbtree | 688 | — | ~715 | Automated safety check: Pass | MIT | |
| Bug Remediation ArchitectGulajavaMinistudio/Mayukai-Theme | 139 | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
OpenLogi macOS Permissions Triage
AprilNEA/OpenLogi
Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.
The Art of Debugging
stas00/the-art-of-debugging
Condensed debugging method and tool recipes for Unix, Python and PyTorch programs: crashes, hangs, segfaults, wrong output, CUDA OOM, NaN values and slowness.
Debug
gnomeria/usbtree
Systematic root-cause debugging — reproduce, isolate, fix at the source, prove the fix.
Bug Remediation Architect
GulajavaMinistudio/Mayukai-Theme
Workflow for analyzing bug reports, tracing root causes, and generating structured bug-fix implementation plans with rollback strategies.
Prp Debug
Wirasm/prp
Diagnoses a bug, error, stack trace, regression, or unexplained behavior and publishes the evidence-backed root cause to GitHub.
More from static-web-server/static-web-server
All 9 skills in this repoDesign
static-web-server/static-web-server
Design or review software architecture, API contracts, data models, and module boundaries for the Static Web Server (SWS) project
Performance
static-web-server/static-web-server
Optimize or review performance for the Static Web Server (SWS) project — profiling, bottlenecks, resource usage, compression, and caching
Prose
static-web-server/static-web-server
Author or edit any prose for the Static Web Server (SWS) project — documentation, design docs, READMEs, PR descriptions, issue bodies, commit message bodies, or other human-readable text — following…
Rust Backend
static-web-server/static-web-server
Write or review Rust backend code for the Static Web Server (SWS) project — crates, modules, functions, types, error handling, and async code
Static File Serving
static-web-server/static-web-server
Serve static files and web assets with optimal headers, MIME types, compression, and caching for the Static Web Server (SWS) project
Testing
static-web-server/static-web-server
Write or review tests for the Static Web Server (SWS) project — unit tests, integration tests, test fixtures, and mocking strategies
Related
Categories
Questions about Issue Tracking
What does Issue Tracking do?
Triage, debug, fix, and document issues for the Static Web Server (SWS) project — bug reports, root cause analysis, fix implementation, and regression prevention. Issue Tracking is an agent skill from static-web-server/static-web-server.
When should I use Issue Tracking?
Issue Tracking fits situations like: tasks that involve Task management; tasks that involve Root cause analysis; tasks that involve QA and bug reports.
How do I install Issue Tracking in Claude Code?
Run `npx skills add static-web-server/static-web-server --skill issue-tracking -a claude-code`. Or copy the skill folder (.agents/skills/issue-tracking in static-web-server/static-web-server) into .claude/skills/issue-tracking in your project. Claude Code loads it when a task matches its description.
How do I install Issue Tracking in Codex?
Run `npx skills add static-web-server/static-web-server --skill issue-tracking -a codex`. Or copy the skill folder (.agents/skills/issue-tracking in static-web-server/static-web-server) into .agents/skills/issue-tracking in your project. Codex loads it when a task matches its description.
Can I use Issue Tracking in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add static-web-server/static-web-server --skill issue-tracking -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue-tracking, .gemini/skills/issue-tracking, .github/skills/issue-tracking and .opencode/skills/issue-tracking in your project.
What does Issue Tracking need to run?
Going by SKILL.md and its folder, Issue Tracking needs the command-line tools its instructions call (curl and openssl).
Does Issue Tracking access the network?
SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Issue Tracking safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Issue Tracking use?
Issue Tracking is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Issue Tracking use?
About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Issue Tracking?
Skills that share tags, products or a category with Issue Tracking: OpenLogi Device Diagnosis (AprilNEA/OpenLogi, 23k stars), OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars), The Art of Debugging (stas00/the-art-of-debugging, 1.7k stars) and Debug (gnomeria/usbtree, 688 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Issue Tracking?
static-web-server (a GitHub organization) maintains it in static-web-server/static-web-server, which has 2,373 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 5, 2026.
Source: static-web-server/static-web-server on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.