Comments
Code comments and annotations
by imoonkey
```
by imoonkey
Upstream typos: destory (not destroy) — unbookmarkPost POSTs to /ajax/statuses/destoryFavorites and unfollowUser POSTs to /ajax/friendships/destory. Both spellings are wrong (Weibo's typo); using the "correct" destroy returns HTML 404. Param name is also asymmetric — followUser takes friend_uid, unfollowUser takes uid.
YouTube
by imoonkey
```
code-review-expert
by sanyuan0704
"Expert code review of current git changes with a senior engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements."
re-frame2
by day8
Writes re-frame2 ClojureScript application code — events, subscriptions, effects, flows, frames, state machines (reg-machine, parallel regions, tags, spawn), schemas, stories, routing, tests, and the canonical patterns (RemoteData, Resources, Forms, Boot, WebSocket, NineStates, ManagedHTTP, AsyncEffect, StaleDetection, FormAction). Authoring only. Do not use for: live-app inspection (re-frame2-pair), greenfield bootstrap (re-frame2-setup), v1→v2 migration (re-frame-migration), porting Reagent views onto Fresco (reagent-migration), or porting re-frame2 itself (re-frame2-implementor). Use whenever the user mentions re-frame2, reg-event, reg-sub, reg-fx, reg-cofx, reg-flow, reg-view, reg-machine, reg-route, reg-resource, reg-mutation, dispatch, subscribe, app-db, flows, frames, regions, tags, the nine UI states, managed HTTP, RemoteData lifecycles, cached server-state / query-cache / TanStack-Query shapes, or tests for a re-frame2 app — even when re-frame2 is not named explicitly.
re-frame2-improver
by day8
Focused critique-mode for existing re-frame2 ClojureScript code: reviews source files (or a supplied snippet) against a small catalogue of re-frame2 anti-patterns, surfaces concrete findings cross-linked to canonical idioms, and may suggest inline fixes. Do not use for greenfield bootstrap, authoring new code, live-runtime work, retro on a pair session, migrating a re-frame v1.x codebase, porting Reagent views to Fresco (a migration ask even on an already-re-frame2 app), touring the Xray devtools panel, porting re-frame2 itself, spec/architecture discussion, or inline mid-edit interruption. Activates only on explicit pull — "review my re-frame2 code for anti-patterns", "audit this against re-frame2 best practices", "spot any anti-patterns in cart/handlers.cljs" — and a body of re-frame2 source must be in scope: read or edited in this conversation, supplied as a snippet, or named as a resolvable .cljs / .cljc file or directory. Vocabulary alone is not enough.
publora-api
by publora
Use this skill when scheduling, publishing, or managing social media posts across multiple platforms (Twitter/X, LinkedIn, Instagram, Threads, TikTok, YouTube, Facebook, Bluesky, Mastodon, Telegram) via the Publora REST API. Also use for retrieving LinkedIn analytics and managing workspace users.
lobster-use
by the-omics-os
Runs bioinformatics analysis with Lobster AI -- single-cell RNA-seq, bulk RNA-seq, genomics (VCF/GWAS), proteomics (mass spec/affinity), metabolomics (LC-MS/GC-MS/NMR), machine learning (feature selection, survival analysis), drug discovery, literature search, dataset discovery, and visualization. Use when working with biological data, omics analysis, or bioinformatics tasks. Covers: H5AD, CSV, VCF, PLINK, 10X, mzML formats, GEO/SRA/PRIDE/MetaboLights accessions. TRIGGER PHRASES: "analyze cells", "search PubMed", "download GEO", "run QC", "cluster", "find markers", "differential expression", "UMAP", "volcano plot", "single-cell", "RNA-seq", "VCF", "GWAS", "proteomics", "mass spec", "metabolomics", "MetaboLights", "LC-MS", "metabolite", "feature selection", "survival analysis", "biomarker", "bioinformatics", "drug discovery", "pharmacogenomics", "variant annotation" ASSUMES: Lobster is installed and configured. For setup issues, tell user to run lobster config-test and fix any errors before proceeding.
documentation
by cosmix
Creates and maintains technical documentation including API docs, README files, architecture docs, changelogs, ADRs, and inline code comments. Handles all documentation needs from code-level docstrings to project-level guides. Trigger keywords: documentation, docs, document, README, tutorial, guide, reference, changelog, ADR, architecture decision record, docstring, JSDoc, rustdoc, pydoc, markdown, mdx, api docs, user guide, developer guide, inline comments, code comments.
bdi-mental-states
by guanyang
This skill should be used when the user asks to "model agent mental states", "implement BDI architecture", "create belief-desire-intention models", "transform RDF to beliefs", "build cognitive agent", or mentions BDI ontology, mental state modeling, rational agency, or neuro-symbolic AI integration.
grafana
by cosmix
Observability visualization with Grafana and LGTM stack. Dashboard design, panel configuration, alerting, variables/templating, and data sources. USE WHEN: Creating Grafana dashboards, configuring panels and visualizations, writing LogQL/TraceQL queries, setting up Grafana data sources, configuring dashboard variables and templates, building Grafana alerts. DO NOT USE: For writing PromQL queries (use /prometheus), for alerting rule strategy (use /prometheus), for general observability architecture (use senior-software-engineer with infrastructure focus). TRIGGERS: grafana, dashboard, panel, visualization, logql, traceql, loki, tempo, mimir, data source, annotation, variable, template, row, stat, graph, table, heatmap, gauge, bar chart, pie chart, time series, logs panel, traces panel, LGTM stack.
senior-engineering-partner
by bjgreenberg
"A strict code reviewer, pair programmer, debugger, and mentor for Python, Bash, Google Apps Script, JavaScript, and Swift/Apple platforms. Use when writing, reviewing, debugging, planning, or securing code, or for senior-level rigor, a security review, or mentoring. Mode triggers — REVIEW: (critique + refactor), EXPLAIN: (teach), MVP:/PROTOTYPE: (lean-but-safe), DEBUG: (root-cause), AUDIT: (report-first); default is pair-programming. Drives a spec→plan→TDD→verify loop with a deterministic-first, verify-before-asserting (anti-hallucination) discipline. Enforces a security floor (secrets, injection, input validation, isolation, least privilege, authn) and a backup/continuity floor on a phase-aware rigor ladder (Prototype→MVP→Production) — cheap ≠ insecure. Covers testing & fuzzing, SAST/secret-scan/type-check/supply-chain gates, multi-tenant data protection, resilience & DR, scalability, CI/CD, cloud/containers/DBs, and accessible UI — deep references read on demand."
codex-explain
by sd0xdev
"Explain complex code via Codex MCP. Use when: understanding complex logic, tracing data flow, onboarding to unfamiliar code. Not for: code review (use codex-code-review), exploration (use code-explore). Output: structured explanation at chosen depth."
Douban
by imoonkey
```
reddit-customer-insights
by sandbaseai
Discover evidence-backed customer language, pain points, objections, and buying triggers from relevant Reddit communities. Use when asked for Reddit research, voice-of-customer analysis, audience pain points, product feedback, or community-led content opportunities.
four-risks
by breethomas
Run Marty Cagan's Four Risks assessment on an issue (value, usability, feasibility, viability). Use when evaluating features before building.
dsh-find-simplifications
by ZK-Andy
'Use when working in the deepseek-harness repo to find non-obvious simplification candidates, write proposed Agent Notes or inline TODO/FIXME/XXX notes, audit or coalesce superseded Agent Notes, or fold worthwhile simplification ideas from another PR; especially for dead, duplicated, speculative, over-built, added-then-removed, or hand-rolled-where-a-dependency-exists surfaces.'
dsh-prose-standard
by ZK-Andy
Use when writing, reviewing, restoring, trimming, or auditing prose in the deepseek-harness repo, including deciding where documentation or comments are required across Markdown, JSDoc, code and test comments, prompts, descriptions, diagnostics, and CLI or UI strings.
dsh-trim-cot-leakage
by ZK-Andy
Use when auditing or fixing prose that reads like a leaked reasoning transcript — dead design-session citations such as (decision N), audit item codes, or §N of uncommitted drafts; change narration such as "used to", "no longer", "this cut"; stack or review vantage ("a later PR in this stack", "rejected in review"); reviewer-addressed justifications; control-flow narration; or hedged planning residue in comments, JSDoc, docs, or Agent Notes.
SKILL.md — ida-rpc
by bkerler
The wire format ({"id", "cmd", "args"} → {"id", "ok", "result/error"}) is designed to be compatible with ghidra-rpc. If you have existing clients built for Ghidra, point them at the IDA socket path and most read-only commands will work with minimal or no changes.
reddit-reader
by brisyramshere
通过 Reddit OAuth2 API 搜索和阅读 Reddit 帖子、评论和子版块内容。当用户要求搜索 Reddit 讨论、浏览子版块帖子、阅读 Reddit 帖子内容和评论、了解 Reddit 社区对某个话题的看法时使用此 skill。支持按时间范围和排序方式筛选，支持读取完整帖子正文和嵌套评论树。
chimera-budget-the-context
by brcampidelli
Spend against a budget below the real window, and count the tool schemas you re-send on every step — they are the floor compaction cannot reach.
loom-builder
by rjwalters
"Implements issues labeled loom:issue (human-approved work)"
loom-curator
by rjwalters
"Enhances approved issues and prepares them for implementation"