Docs & Writing

joneqian Skill

Search the web using Baidu AI Search Engine (BDSE). Use for live information, documentation, or research topics.

joneqian Skill

Web search and content extraction via Brave Search API. Use for searching documentation, facts, or any web content. Lightweight, no browser required.

juicesharp Skill

Surgically repair a working tree whose validate run returned a failing verdict — re-run each failed verify-at-implement risk ruling's prescribed procedure and each structured blocker's failing command, apply the minimal localized code fix grounded in the validation report, then confirm it passes. Single-pass, no subagents, no self-review, no questions. Workflow-gated repair arm dispatched after a failing validate; use as a gate's repair stage.

juicesharp Bundle

Generate CLAUDE.md files placed inline next to source code across a project, documenting architecture and patterns for AI assistants. Use when the user wants to onboard Claude to a codebase via inline CLAUDE.md files, generate per-directory guidance, document architecture in-place, or asks to "annotate inline". Prefer this over annotate-guidance when CLAUDE.md should live alongside the code rather than in a shadow tree.

juicesharp Bundle

Generate architecture.md guidance files under .rpiv/guidance/ that document a project's architecture and patterns for AI assistants, written to a shadow tree alongside the source. Use when the user wants to onboard Claude, Cursor, or an AI agent to a codebase via the guidance system, document architecture, or asks to "annotate guidance". Prefer this over annotate-inline when the project uses the .rpiv/guidance/ shadow tree instead of inline CLAUDE.md files.

karim-bhalwani Skill

Editor sub-role of the data-narrative skill. Reads analyst.json and detective.json, selects a single compelling narrative angle, ranks findings by story priority, and drafts the structured report.md. Loaded and invoked by the data-narrative orchestrator only.

karim-bhalwani Bundle

Inspector sub-role of the data-narrative skill. Links every claim in report.md back to its upstream evidence (Analyst code line or Detective source URL). Produces inspector.json - the machine-verifiable provenance manifest for the narrative. Loaded and invoked by the data-narrative orchestrator only.

ldaume Skill

Designs and reviews REST, GraphQL, and internal APIs with explicit contracts, validation, errors, pagination, versioning, documentation, auth, and compatibility. Use when creating endpoints, changing API contracts, writing OpenAPI docs, reviewing GraphQL schemas, or refactoring service boundaries.

ldaume Skill

Writes and updates durable project documentation, decision records, runbooks, and architecture notes for a clear reader or operational purpose. Use when making architecture decisions, changing public APIs, adding operational procedures, documenting trade-offs, or deciding whether a change needs an ADR.

legioncodeinc Bundle

Trigger on who has not paid me, chase unpaid invoices, accounts receivable, overdue invoice, aging report, payment follow up, outstanding invoices, invoice reminder, who owes me money, collections, past due. Rebuilds a receipted receivables table from Littlebird capture of invoices the user sent, reconciles it against every payment observation it can find, buckets what is left by age, forces a verification step before calling anything overdue, and drafts a polite-to-firm follow-up ladder per client that is held for approval and never sent.

legioncodeinc Bundle

Weekly attention forensics from Littlebird capture. Trigger on how fragmented was my week, where did my attention go, focus report, am I context switching too much, what broke up my week, rabbit hole check, weekly focus review, why did I get nothing done. Counts observed switches between work contexts, run length in consecutive snapshots, fragmentation by hour of day, named rabbit holes against stated intentions, and meeting load against unbroken calendar time. Ships week-over-week change plus one behavioral experiment to try. Never produces hours lost, percentages of the day, or a productivity score, because periodic snapshots cannot measure those. Self-analysis only, never pointed at another person.

legioncodeinc Bundle

Turn one long-form artifact into a week of voice-matched derivatives that each take a different angle. Trigger on 'repurpose this post', 'turn this into a week of content', 'make content from this call', 'break this down for LinkedIn', 'I need a content pack', 'what else can I do with this webinar'. Produces 5 to 7 standalone short posts, a carousel outline with per-slide copy, an email, a thread, a sequencing plan with reasons, and a mandatory do-not-publish list. Enforces a seven-angle taxonomy so the pack is genuine variety and not the same idea five times. Drafts through the user's own voice skill when one is installed. Never publishes and never posts.

lklimek Skill

This skill should be used when emitting or consuming review findings. It defines the unified review report format for all finding-producing agents.

lklimek Bundle

This skill should be used when the user asks to "check PR comments", "verify review comments are addressed", or otherwise confirm that PR feedback is resolved in code. It can optionally produce a triage-compatible report.

mesh-llm Skill

Use this skill when running benchmark orchestration, local single-stage or split benchmarks, benchmark report flow, or performance-oriented skippy runtime checks.

mesh-llm Skill

Use this skill when working on benchmark telemetry ingest, metrics-server run lifecycle, OTLP collection, SQLite storage, benchmark report export, or separating telemetry/reporting ownership from staged runtime servers.

full-stack-skills Bundle

Configure, operate, diagnose, and automate Cargo for Rust packages and workspaces. Cover manifests and targets, commands, dependency resolution and features, profiles, build scripts, configuration and environment variables, caches and build diagnostics, cross-compilation, registries, packaging, publishing, metadata, CI reproducibility, and stable-versus-nightly feature gates. Use for Cargo.toml, Cargo.lock, .cargo/config.toml, cargo build/check/run/tree/metadata/package/publish, resolver or feature problems, build output and performance, private registries, and beginner Cargo workflows. Route crate selection and supply-chain audits to rust-dependencies, workspace topology to rust-workspace, test design to rust-testing, documentation design to rust-documentation, lint policy to rust-style-clippy, and API compatibility decisions to rust-semver.

full-stack-skills Bundle

Review Rust changes for correctness, memory and thread safety, error semantics, unnecessary allocation or cloning, lock scope, API compatibility, test gaps, documentation, and dependency risk, applying the Rust API Guidelines checklist (C-PANIC, C-UNWRAP, C-TRANSMUTE, C-BOOL, C-NEWTYPE, C-COMMON-TRAITS, C-CONVERT, C-SEALED, C-NON-EXHAUSTIVE). Use when reviewing Rust diffs, pull requests, libraries, unsafe boundaries, or production incidents; report actionable findings by severity before summaries, route automated formatting or lint policy to rust-style-clippy, and route API shape decisions (trait sealing, error taxonomy, newtype design, builder patterns) to rust-api-design.

full-stack-skills Bundle

Measure, profile, optimize, and regression-test Rust performance across latency, throughput, CPU, allocations, memory, binary size, and compile time using representative workloads, Criterion, iai-callgrind, cargo-flamegraph, samply, DHAT, heap or pprof tools, cargo-bloat, cargo-llvm-lines, and build timings. Use when users report slow Rust code, high memory or CPU, large binaries, noisy benchmarks, tail-latency regressions, or need performance budgets and evidence-backed optimization.

full-stack-skills Bundle

Design, write, build, test, and publish Rust documentation with rustdoc, cargo doc, doctests, intra-doc links, crate-level guides, examples, README synchronization, mdBook, docs.rs metadata, link checking, documentation CI, and the Rust API Guidelines Documentation chapter (C-DOC, C-LINK, C-META, C-EXAMPLE). Use when users ask for Rust API docs, a project book, runnable examples, docs.rs readiness, missing-doc policy, API guideline compliance, documentation architecture, or stale documentation repair.

gitbyeos Bundle

按地点与活动半径查周边天气与空气质量，输出 Markdown 报告与出门防护建议。用户提及「周边天气」「天气咋样」「出门建议」时使用。

hoetaek Bundle

Use at each phase boundary (and before user review or gate close) to make the cumulative LEAF document — all phases so far read as one connected report — read simply and flow naturally, not as draft notes. Preserve source truth while removing stale options, process chatter, duplicate reasoning, status drift, or doctor-reported legacy layout/status fields. Do not use to create the artifact, decide press/fall close-out, or maintain execution artifacts.

impertio-studio Bundle

Use when generating an OpenAPI 3 specification and a Swagger UI for an Axum service: documenting handlers, describing request and response schemas, or serving an interactive API explorer. Prevents the hand-written spec that silently drifts from the real handlers, the route registered on the Router but missing from the spec, the wrong {param} versus :id path syntax, and pinning three independently-versioned crates to mismatched releases. Covers utoipa derive macros ToSchema, OpenApi, IntoParams, IntoResponses, ToResponse, the #[utoipa::path] attribute, utoipa-swagger-ui SwaggerUi, and utoipa-axum OpenApiRouter with the routes! macro that registers a handler once for both routing and the spec. Keywords: axum openapi, utoipa, utoipa-axum, utoipa-swagger-ui, ToSchema, utoipa::path macro, derive OpenApi, OpenApiRouter, routes macro, split_for_parts, SwaggerUi, swagger ui, api documentation drift, spec out of date, route documented but returns 404, schema missing from spec, swagger ui blank page, how do I add swagg

shader-slang Skill

Read and write SlangPy documentation.

shader-slang Bundle

Write-heavy Slang release engineering: update the SPIRV-Tools/SPIRV-Headers submodules and integrate GitHub master into the internal GitLab forks (the slang + slang-rhi + slangpy OptiX triad). Use when cutting a release, syncing SPIRV, or rebasing the GitLab nv-* branches. Invoke via /slang-release. This skill performs destructive git operations (force-pushes) and always confirms first. For read-only maintainer reporting (daily report, release notes drafting, issue prioritization), use slang-maintainer-tools instead.

shader-slang Bundle

Surface the open shader-slang PRs needing human attention with a bundled gh-only Python script (scripts/pr_report.py): an assignee-grouped escalation report computed entirely from live GitHub state (read-only; no writes; optional Discord/Slack mentions). Use for PR triage, the reviewer-attention report, stale-PR follow-up, or a scheduled report run.

sirkirby Skill

Generate a sanitized UniFi Access support bundle, help the user review it locally, and prepare it for a bug report without posting it

sirkirby Skill

Generate a sanitized UniFi Network support bundle, help the user review it locally, and prepare it for a bug report without posting it

sirkirby Skill

Generate a sanitized UniFi Protect support bundle, help the user review it locally, and prepare it for a bug report without posting it

skills-il Bundle

Interactive workflow for creating new skills for the skills-il organization. Guides through category selection, use case definition, folder scaffolding, metadata.json generation with bilingual metadata, instruction writing, Hebrew companion creation, and validation. Use when user asks to create a new skill, scaffold a skill for skills-il, write a SKILL.md, contribute a skill, new skill template, or liztor skill chadash. Enforces skills-il conventions (kebab-case naming, Hebrew transliterations, bilingual display names, progressive disclosure, validate-skill.sh compliance). Do NOT use for editing existing skills, creating skills for non-skills-il platforms, or generic markdown file creation.

vemodalen-x Bundle

Bump a device/library's four-segment version after an acceptance build+run passes, and keep the version single-sourced. The four segments X.Y.Z.W are embedded in three agreeing surfaces — a source string constant, the init log line, and a getVersion() API. Bump rules: W (last) = bug-fix +1; Z (penultimate) = feature +1 and reset W to 0; both-in-one-release = Z +1 and reset W to 0; X.Y (first two) = major/platform-line, human-set only. Precondition: the acceptance build+run has already succeeded. After bumping, report old → new explicitly. Use when releasing a library and the version must advance. Identity-decoupled — the version-string field name + file are caller parameters; no project names embedded.

vemodalen-x Bundle

Publish a project deliverable (proposal / research report / experiment report / design doc) to the project's Feishu (Lark) wiki as a clean technical-report-styled document — tables and flowcharts for structured info. Use when a stage produces a deliverable that should be filed to the team Feishu wiki. Owned by Framework 0 (orchestration); style is constrained by ml-paper-writing + the local style spec.

vemodalen-x Bundle

Staff a team group chat — when someone @-mentions the bot, read what they asked and reply to that need. Pull new messages by cursor (per-instance cursor file), filter for @bot mentions since last handled, triage the request (report / data / status / question / over-authority decision), serve what is serviceable (send a file or link as the bot, answer numbers ONLY by quoting the named ledger/report — never fabricate), reply to the asker with a post @-tag, in instance-policy Chinese (via polishing-chinese-prose). Decision-class requests escalate ("已转负责人" + @user), never auto-answered. Use to run group-chat attendance / answer @bot mentions on demand. Identity-decoupled — group id, bot/user identity, cursor + wordlist paths, open_id map are instance values.

mesh-llm Bundle

Use this skill when validating a MeshLLM release candidate or current HEAD against the last GitHub release, assembling the canonical feature/fix/modification inventory, testing locally built release bundles on user-approved real hosts and private meshes, deciding release readiness, or producing a formal evidence-backed release-validation report.

moonlarry Bundle

Draft paper content section by section from a paper plan, first as complete Markdown drafts and then as one LaTeX file per section. Use when user says \"写论文\", \"write paper\", \"draft LaTeX\", \"开始写\", wants Markdown-first paper drafting, or wants to generate LaTeX content from a problem-aligned paper plan.

moonlarry Bundle

Refine academic writing at the paragraph level. Use when the user wants English LaTeX polishing, Chinese paper polishing, shortening, expansion, or de-AI rewriting for LaTeX or Word-ready text.