Trending Skills
The hottest skills gaining momentum in the community right now.
review-r
by pedrohcgs
Read-only R code review protocol for .R scripts. Checks code quality, reproducibility, domain correctness, tidyverse idioms, and professional standards; produces a report without editing. Use when user says "review this R script", "check the R code", "audit the analysis code", "code review on the R", or when an R file is touched as part of a paper submission. NOT for running the code — pair with /audit-reproducibility for numeric verification.
adjudicate-review
by pedrohcgs
Turn an incoming set of findings — from an AI reviewer, a referee report, a code review, a linter, or a second model — into verified fixes, without letting a confident misread damage correct work. Every finding is a CANDIDATE until checked against the actual source. Use whenever you receive review comments, audit findings, or a critique you did not write yourself, especially when the reviewer is a model or when the volume is too large to check by feel.
stata-replication
by pedrohcgs
End-to-end Stata replication pipeline — scaffolds numbered .do files in scripts/stata/, executes them via the stata-mcp MCP server, captures logs and outputs to scripts/stata/_outputs/, and produces publication-ready tables (esttab) and figures (graph export). Mirrors /data-analysis for R-first projects. Use when user says "stata replication", "set up Stata pipeline", "scaffold the .do files", "run Stata analysis", "AEA replication package in Stata", or when a project's analysis language is Stata not R.
data-analysis
by pedrohcgs
End-to-end R data analysis pipeline — exploration → cleaning → regression → publication-ready tables and figures. Use when user says "analyze this dataset", "run a regression on X", "explore this CSV", "full analysis workflow", "get me summary stats and a regression", or points at a .csv/.rds/.dta and asks for empirical results. Produces numbered R scripts in scripts/R/ and outputs to scripts/R/_outputs/.
lit-review
by pedrohcgs
Structured literature search + synthesis with citation extraction, thematic clustering, and gap identification. Use when user says "find papers on X", "do a lit review", "what's the literature on...", "summarize what we know about...", "where's the gap in this field", "review recent work on Y". Produces a written review with BibTeX-ready citations. Uses WebSearch/WebFetch for recent work.
data-management-plan
by pedrohcgs
Draft a funder-compliant Data Management Plan (NSF DMP, NIH DMS Policy 2023, ERC, Horizon Europe) by composing the confidential-data and environment-capture primitives. Sections cover data description, formats/metadata, storage/backup, access/sharing, preservation/archiving, and roles. Use when user says "data management plan", "DMP", "DMSP", "NIH data sharing plan", "write the data plan for my grant", or when a grant proposal needs a data-management section. NOT a submission tool — produces a draft the user pastes into the funder portal (DMPTool, NIH ASSIST, Horizon Europe portal).
literature-review
by IncarnaMind
Writes a literature review across the User's Documents on the Question's topic, synthesised by theme rather than one Document after another, showing where the Documents agree and disagree and what they leave out, with every claim cited. Use when the User asks for a literature review, a review of related work, a state-of-the-art overview or a synthesis of several Documents.
summarise-document
by IncarnaMind
Writes a structured summary of one Document, or of each Document in the Question's Search scope, with sections that suit the kind of Document (a paper's claims, method and limitations; an agreement's parties, term and obligations) and each point with a Citation. Use when the User asks to summarise, digest or give an overview of a paper, report, contract or other Document.
mind-to-report
by IncarnaMind
Turns the User's Mind, meaning the Notes, Questions and earlier Answers above the Question, into a structured report draft with a title, a summary, sections and a conclusion, keeping their Citations and inventing no sources. Use when the User asks to write up, draft a report, compile or turn their notes or this Mind into a document.
typescript-advanced-types
by jasonraimondi
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.
tuist-swift-review
by tuist
Project-specific pull request review rules for the tuist/tuist Swift codebases. Focuses on the things only this repo knows, including preferring value types, the testing framework choice, and migration of XCTest to Swift Testing.
establishing-code-ownership
by PostHog
Determine which PostHog team owns a file, directory, or code path, or enumerate all code a team owns (via distributed owners.yaml, products/*/product.yaml, and .github/CODEOWNERS). Use when assigning a reviewer, attributing a bug or slow query to a team, routing work, scoping a team-wide audit, or answering "who owns X" / "what does team Y own".
1k-dev-commands
by OneKeyHQ
OneKey development commands plus branch, commit, validation, and PR conventions.
1k-perf-optimizer
by OneKeyHQ
"Diagnose and optimize OneKey iOS startup and Wallet Home performance using timing metrics, call counts, profiling, and regression baselines."
1k-trade-swap-market
by OneKeyHQ
Implement and debug OneKey Swap, Bridge, Limit, and Stock/Market trades, including quotes, review, execution, fees, and history. Excludes Perps and chart communication.
1k-i18n
by OneKeyHQ
OneKey i18n and Lokalise workflow for module copy, full-language translation create/update, bilingual previews, confirmed upload, pull, and verification. Never edit generated translations.
1k-auditing-pre-release-security
by OneKeyHQ
Audits security and supply-chain risk between two git refs with Codex cross-validation. 预发布安全审计（含 Codex 交叉验证）。Use when performing pre-release security audits, supply-chain reviews, or comparing two git refs for security regressions. Triggers on “预发布审计”, “security audit”, “release audit”, “安全预审”.
1k-ui-recipes
by OneKeyHQ
Reference-only catalog of UI workaround recipes. Do NOT auto-load — invoke ONLY when the user explicitly asks for "1k-ui-recipes" or a specific recipe by name (iOS tab bar scroll offset, collapsible tab horizontal scroll, Android bottom tab touch intercept, keyboard avoidance, iOS overlay navigation freeze, web keyboardDismissMode, iOS modal Fabric frame animation, Android background thread timers/microtasks).
1k-implementing-figma-designs
by OneKeyHQ
Implements Figma designs 1:1 using OneKey component library (还原设计稿).
1k-browser-module
by OneKeyHQ
OneKey Browser/Discovery development for WebView tabs, bookmarks, history, search, URL risk checks, DApp connections, and JSBridge behavior.
1k-platform-requirements
by OneKeyHQ
Minimum SDK/OS version requirements for all OneKey platforms (iOS, Android, Chrome, Electron).
adding-inbound-webhooks
by PostHog
Use when adding a webhook endpoint for a third party that sends to PostHog, adding an inbound webhook consumer for a provider that already has an endpoint, or migrating a hand-rolled hmac verifier that the inbound-webhooks-go-through-ingress semgrep rule flags. Covers the two jobs separately: a consumer in products/<product>/backend/webhook_consumers.py, and a provider incarnation under posthog/ingress/<provider>/ wired with build_webhook_view(). Carries the rules that are easy to get wrong: a consumer name is a dedup cache key, event types must be declared by the provider app or the registry raises, and the module stays cheap to import. Trigger terms: add a webhook, webhook consumer, inbound webhook, hand-rolled hmac, inbound-webhooks-go-through-ingress.
claude-code-plugins
by melodic-software
"Verify and configure the codebase-health plugin for this repository. check inspects the tracked .claude/codebase-health.md config read-only across its merge layers (presence, dimension source lists, tracked-not-ignored); apply interviews the user, infers audit targets from the repo layout, and writes the config. Use when: 'set up codebase-health', 'is codebase-health configured', 'configure the audit', 'codebase-health setup', the audit skill reports missing or thin config, or audit dimensions need tuning. Re-runnable. Safe to invoke again to reconfigure."
Recheck against upstream
by melodic-software
"Re-anchor the discipline that existing state (config, code, docs, infra) is not evidence of its own correctness; audit it against CURRENT official upstream docs. Use when: 'recheck against upstream', 'check this against the docs', 'is our config still current', 'did upstream change', 'are we still doing this right', 'verify against the official docs', 'this may have drifted from upstream', 'audit our setup against the vendor docs', or at conversation start on config, infra, or integration work."