All authors

Claude Skills by HiQS-Labs
github.com/HiQS-Labs80 skills0 installs3 views
- Weekly ShippedSummarize what shipped to `main` over the last week as a concise, human- sounding end-user report. Use when the user wants "this week's shipped improvements", "top things that landed", or a weekly release-style recap from git history, especially when they want the answer framed around everyday user impact instead of commit mechanics.Votes: 0GitHub stars: 5
- Whack A MoleFind the class of bugs that keeps coming back and file one umbrella issue to fix the root cause instead of the symptoms. Scans the last 14 days of GitHub issues, fix/revert commits, and PR review threads, clusters related bugs, ranks clusters by a composite churn score (reopens, repeat fixes on the same files, comment volume, time open, cluster size), then uses debug-mantra and deep-recon skills (if installed) to understand the top cluster and drafts a GH umbrella issue with a remediation tas...Votes: 0GitHub stars: 5
- AteATE (Automated Testing Environment): drive long-running (2-3hr+) unattended variation-test suites against the Aider, OpenRouter, and GLM 5.2 pipeline using a local Gemma model in LM Studio as the worker, with periodic frontier-model check-ins for drift control, ending in a single triaged GitHub issue. Use this whenever the user wants to \"run variation tests overnight/for hours\", \"debug a bunch of small Aider bugs\", \"test Aider flag combinations\", \"fuzz the Aider harness\", mentions LM ...Votes: 0GitHub stars: 5
- BrowserbaseGive an AI agent a real cloud browser (Browserbase) for web research, scraping, page fetching, web search, form-driving, and site monitoring, with the API key loaded by path from ~/secrets/browserbase.txt and never written into the repo. Routes each task to the lightest capability (Fetch -> Search -> browse.sh skill catalog -> Stagehand act/extract/observe -> raw Playwright session) and returns structured, cited results. Trigger on /browserbase, "use Browserbase", "research this on the web", ...Votes: 0GitHub stars: 5
- Ci DoctorDiagnose CI health and, when needed, benchmark a config change side by side — without re-deriving either from scratch each time. Use when the operator asks "why is CI slow", "diagnose our CI", "is our CI healthy", "what's the bottleneck", or wants to compare wall-clock across two or more `runs-on` (or other config) variants — e.g. GitHub-hosted vs. a paid runner vendor, or a small vs. large runner tier. Not for writing new workflows from scratch, not for non-GitHub-Actions CI systems, not for...Votes: 0GitHub stars: 5
- Ci OptimizeAudit, harden, and optimize CI/CD pipelines across diverse repositories using production-tested, zero-cost principles. Use when an operator asks to "audit our CI/CD", "speed up test runs", "fix flaky CI", "harden pre-push gates", "design CI tiering", "eliminate test contention", or evaluate CI architecture before investing in costly runners or complex tooling. Provides a structured 12-point audit rubric, failure prevention mechanisms, and a phased adoption roadmap calibrated to repository risk.Votes: 0GitHub stars: 5
- FeynmanConvert a highly technical document or subject into a plain, accurate, layman-friendly explanation using Feynman-style teaching moves — everyday analogy, a first-principles ladder, jargon stripping, and honesty about the limits. Use this whenever the user wants to "explain this simply", "make this understandable to a non-technical audience", "translate this for stakeholders / execs / new hires / customers", "ELI5 this doc", "de-jargon this", give me the "plain-English version", "what does thi...Votes: 0GitHub stars: 5
- Front DoorWalk a repo's front door as a brand-new user would and report whether they can actually get from clone to working — not just whether the docs exist. Use whenever the user asks to audit, review, or critique a repo's onboarding, installation, setup, getting-started, or quickstart experience; asks "can a new user install this," "is the setup too hard," "why is onboarding so painful," "are there too many READMEs," "which doc is the source of truth," "did we leak an API key," or wants install scri...Votes: 0GitHub stars: 5
- Github Auth DebugDiagnose and fix the "git push works but `gh` fails" auth split on macOS — where the GitHub CLI and git consult different credential stores and drift apart — non-destructively, without over-engineering. Trigger when the user says "git push works but gh fails", "gh auth is broken", "token in keyring is invalid", "gh auth status fails", "fix/unify gh and git auth", "re-auth GitHub CLI", "gh 403 SSO/SAML", or when a `gh` command fails mid-session with an auth/keyring/TLS error while `git` still ...Votes: 0GitHub stars: 5
- Install Improve AuditGet an unfamiliar repo installing and building locally, fix only what blocks it, and open a PR carrying the fixes plus an append-only change log. The deliverable is a working build and a PR — never a findings report. Trigger when the user says "install this repo", "get this building", "clone and set this up", "make this run locally", "why won't this build", "docker compose build fails", "/install-improve-audit", or hands over a repo path or URL and asks for it working. Container-native repos ...Votes: 0GitHub stars: 5
- Open RouterResolve a colloquial OpenRouter model name (e.g. "GLM 5.2", "Nemotron Ultra 3") to its canonical `provider/slug[:variant]` id BEFORE setting `AIDER_MODEL` for `aider-turn.sh`, `consult.sh --models aider`, or `DEEP_RESEARCH_OPENROUTER_MODEL` for `deep-research.mjs --provider openrouter`. Checks the local alias table (`relay-automation/openrouter-model-aliases.yml` via `resolve-model-alias.sh`, GH-120) first — zero network calls — and only falls back to the live `openrouter.ai/api/v1/models` ca...Votes: 0GitHub stars: 5
- Read OnlyAdd a curated set of read-only permission rules -- file reads, directory listings, content search (grep/glob), git inspection, and system checks -- to a Claude Code settings.json allowlist so safe reads stop triggering permission prompts. Local read-only by default; outbound reads (WebFetch, WebSearch, registry lookups) and secret-bearing reads (env dumps) are offered only as explicit opt-ins. Trigger when the user says "read-only", "/read-only", "pre-approve read operations", "allow all read...Votes: 0GitHub stars: 5
- Readme AuditAudit a repo's root README as both the artifact under review and the map to everything else — checking accuracy, legibility, understandability, and operator UX, then following every pointer it makes to other docs as a litmus test for the whole repo's doc hygiene. Use when the user asks to "review/audit/check the README," "is the README accurate," "does the README still match the code," "find gaps in the README," "are our docs drifting," "do the README's links still work," "is the README clear...Votes: 0GitHub stars: 5
- RprReview the most recent permission requests in the current session, generalize them into safe allowlist rules, and append them to .claude/settings.local.json to reduce future prompts. Triggers when the user runs "/rpr", "/rpr <N>", "/rpr session", or says things like "stop asking me", "I keep getting permission prompts", or "reduce these requests". Differentiates from read-only (which pre-approves safe reads) and fewer-permission-prompts (which mines all history) by reacting only to the recent...Votes: 0GitHub stars: 5
- ShakedownAudit a script-calling skill for CWD-sensitive path-resolution bugs — bundled `.sh` scripts that run in the session that wrote them but come back "not found" in another session, repo, or install — then write a graded report with a proposed fix. Runs a read-only static path audit plus a live scenario matrix (foreign CWD, nested dirs, spaces-in-path, project vs user install, stripped exec bit). Use when the user says "test this skill", "shake out the path bugs", "why can't Claude find my skill'...Votes: 0GitHub stars: 5
- Spike 360Interrogate authority before planning a feature, refactor, migration, rewrite, backfill, event-sourcing design, dual-write setup, new authoritative store, or system-of-record change. Fire whenever a proposal might introduce, move, duplicate, or replace authoritative state — or involves event sourcing or "event sourced," a "source of truth," "authoritative" data, dual-writes, replay, projections, replacing persistence, a new data store, or "design the architecture for / rewrite X" — and classi...Votes: 0GitHub stars: 5
- Swe DiagramDraw an interactive system architecture or Git-history diagram for a repo. Architecture maps start from existing rendered knowledge (graphify, codebase-memory, RAG, architecture docs) before raw code. Git-history maps render commits, branch cuts, and merges as stacked lanes from local refs. Produces a JSON spec and self-contained dependency-free HTML with pan/zoom, draggable nodes, typed edges, search, and filtering. Trigger for "draw the system diagram", "diagram this repo/architecture", "vi...Votes: 0GitHub stars: 5
- TimbreWrite copy in a specific human voice using a three-role, layered pipeline — a Cartographer that maps the voice from real samples, a Drafter that writes conditioned on verbatim exemplars, and a blind Adversarial Reader that never sees the voice map and grades against a planted control. Use when the user wants copy that "sounds like me", "sounds human", "matches our brand voice", "doesn't read like AI", "rewrite this in my voice", "humanize this draft", "make this less ChatGPT-ish", or hands ov...Votes: 0GitHub stars: 5
- Vendor StackInstall the full swarm stack into a target repo: vendor the XYZ harness (relay/marathon/consult/self-improve + `tick`) into `<target>/.xyz/`, then optionally install the PDDA doc-governance runtime (`PROJECT/PDDA.md` + `utils/pdda/*.sh`). Both installers self-locate, are idempotent, and register the target into their own per-user upgrade registry so a later `xyz-sync` / `pdda-sync push` can carry updates forward. Trigger on "/vendor-stack", "vendor XYZ (and PDDA) into <repo>", "install the st...Votes: 0GitHub stars: 5
- Vscode ColorGive a git repo a stable, distinct VS Code background tint so windows are tellable apart at a glance. The color is scoped to the workspace (.vscode/settings.json under workbench.colorCustomizations), so it applies every session with no per-session step. Two modes: deterministic (SHA-256 of the repo's GitHub slug -> a hue, same repo always same color) and manual override (the user names a color or feel). Tints seven surfaces — editor, sidebar, activity bar, panel, active tab, title bar, status...Votes: 0GitHub stars: 5
- PddaRe-orient to this repo's PDDA operating order. Walks the ROUTER.md startup sequence, names the canonical next file for the task at hand, and reports current PDDA state (active docs, roadmap coverage, deterministic findings). Use at inflection points — session start, task switch, after /compact, or whenever context has drifted — instead of typing "re-read ROUTER.md".Votes: 0GitHub stars: 5
- 3 COMPLETED| What was just completed | What's next | |---|---| | Codex plan and final QA approved; skill structure and focused PDDA checks passed; full `ci-local.sh` passed in a disposable full clone at `9b3a780d` with 421 suite verdicts and a clean clone-identity invariant | Push the reviewed branch and open a PR to `development`; check hosted CI on the pushed commit |Votes: 0GitHub stars: 5
- 3 COMPLETED| What was just completed | What's next | |---|---| | Five Markdown skills updated; Fable, GLM and targeted Sol QA Approved. | Publish ready PR against development; await review/merge. No installation. |Votes: 0GitHub stars: 5
- HandsfreeKeep the current agent moving on an already-authorized task while CI, tests, reviews, or other asynchronous work finishes. Arm a native same-conversation wake every 10 minutes for at most 3 hours, check live evidence, advance the nearest milestone, and cancel the wake when work ends. Use for "handsfree", "watch this run and continue", or "keep checking CI without my nudges".Votes: 0GitHub stars: 5
- Sanity CheckAssess whether a claimed problem or blocker is real, consequential, and worth fixing now. Use at the first failure that blocks a task, when investigation stops producing evidence, or when asked whether a feature, CI test, or other machinery is necessary. Ground the decision with recon, debug-mantra, and ponytail; defer low-risk work through PRS-rated GitHub intake and propose feature retirement or required-gate changes for operator decision.Votes: 0GitHub stars: 5
- Daily PlannerAdaptive daily planning skill that pivots the active weekly plan based on what closed yesterday. Directly reuses the core engine and adversarial Northstars from weekly-planner (skills/3-weekly/weekly-planner/) to eliminate logic drift and prevent planning contradictions. Re-sequences the daily merge queue and highlights the immediate blocker for the operator.Votes: 0GitHub stars: 5
- Where Are We AtAnswer "where are we at on <topic>?" with a deep ground-truth assessment of a module, feature, or subsystem. Cuts through stale documentation and superficial LLM scans by orchestrating /recon (codebase architecture & live symbols), /debug-mantra (empirical breadcrumb observation), and /merge-cleanup (multi-checkout, active sessions, tick claims, and PR detection) into a verified status report.Votes: 0GitHub stars: 5
- Task SyncUnified IDE task-list grooming for XYZ Forge: one central core with per-IDE adapters (ZCode, Antigravity, Codex desktop) that date-stamp task titles with the task's own last-activity mm-dd, write last-action descriptions, and manage pins under one safety contract. Use when asked to groom/sync IDE task lists, set up the 15-minute heartbeat, install task-sync via Skills Army HQ, or run the health doctor.Votes: 0GitHub stars: 5
- Weekly PlannerDual-horizon weekly planning and team orchestration skill built around XYZ Forge PRS (releases.db) and PDDA, with zero-dependency markdown fallback. Ingests team weekly GitHub issues, maps member focus domains, prioritizes high-value blockers, enforces the Provisional Decisions Protocol (zero stalls on external decisions), performs a rigorous 2nd-pass adversarial conflict and contradiction audit, and outputs a lightweight weekly outline. Shares core engine functions with daily-planner to ensu...Votes: 0GitHub stars: 5
- Ci Suite AuditAudit registered CI test suites and recommend retention, split, nightly, quarantine, or turn-off verdicts based on runtime receipts, failure history, touch-set overlap, and prose/junk assertion analysis. Use when an operator asks to "audit test suites", "curate CI tests", "find slow tests", "identify redundant tests", "review test retention", "evaluate test gate health", or prepare the full-suite audit.Votes: 0GitHub stars: 5