Explore skills
Showing 48631–48660 of 77081 skills
Conduct an independent, adversarial pre-submission audit of an empirical manuscript against editorial fit, claim–evidence alignment, methods and statistics, transparency and reproducibility, theory, citations, and prose. Use for reviewer simulation, desk-rejection risk assessment, red-team review, submission-readiness gates, or producing a prioritized revision memo. Do not use to rewrite the paper, and never resolve an evidence conflict in the authors' favor.
angushushu/shu-academic-writing-skill
Stars: 0Claude CodeCodexOPTIONAL MODULE, heavy dependencies. Compute cohesion, syntactic-density and lexical indices for a draft and express them as percentiles against a reference corpus of the author's target venue. This is an instrument, not a review — it produces norm-referenced evidence for `core/engineer-argument/` and `core/polish-prose/` to interpret, and it does not write feedback on its own. Use when a review needs to say whether a cohesion, complexity or lexical measure is actually unusual for the field rather than merely reporting a raw number; when the author asks how their prose compares to published work in their venue; or when someone wants to build norms from a corpus of articles. Requires spaCy — run `python scripts/tcm.py doctor` first and report honestly if the environment cannot support it.
angushushu/shu-academic-writing-skill
Stars: 0Claude CodeCodexOrchestrate evidence-grounded development of an empirical manuscript: planning, drafting, restructuring, substantive revision, integrating theory with methods and results, reconciling project artifacts, and preparing a submission-ready paper plus supplement. Use when the work spans the whole paper rather than one passage. Do not use for isolated sentence polishing or for an independent adversarial audit.
angushushu/shu-academic-writing-skill
Stars: 0Claude CodeCodexDiagnose why a draft will not land with its readers, using Larry McEnerney's framework — value over clarity, reader-driven prose, instability and cost, community codes. Use when someone shares a paper, abstract, introduction, dissertation chapter, literature review, grant or research proposal, or conference submission and wants feedback, review, critique, or "does this work?" — and when they ask why their writing gets rejected, desk-rejected, ignored, or called boring or unconvincing, how to make an argument compelling, whether their contribution is significant enough, or how to write a stronger intro or abstract. This is the top-down structural review: value, problem, movement, code, and the sentence patterns that follow. For a pure line-level pass on prose whose argument is already settled, read `core/polish-prose/SKILL.md` instead. Default behavior is diagnosis and coaching, never rewriting.
angushushu/shu-academic-writing-skill
Stars: 0Claude CodeCodexDiagnose why prose is hard to read at the sentence and paragraph level, using Joseph Williams's principles — characters as subjects, old before new, the stress position, topic strings, nominalization, hedging, and passive voice used fairly. Use when someone wants writing tightened, clarified, or line-edited, or asks why a passage feels dense, clunky, wordy, stiff, bureaucratic, or hard to follow — methods sections, technical documentation, reports, memos, cover letters, grant prose, and emails, not only academic papers. Also use when someone asks how to cut length without losing content or how to make an already-sound argument easier to read. Default behavior is naming patterns with quoted evidence and drills, not rewriting. If the draft's argument or contribution is what is actually in question, `core/engineer-argument/SKILL.md` handles that layer first.
angushushu/shu-academic-writing-skill
Stars: 0Claude CodeCodexMake a manuscript a reader wants to read: one argument, one stake, no interruptions. Use when a draft is correct but unreadable, when a reviewer says it is dense or hard to follow, or as the first pass before any audit. Do not use it to check numbers, disclose limitations, or verify venue compliance -- that is core/audit-manuscript/SKILL.md, and doing both at once produces a document instead of an argument.
angushushu/shu-academic-writing-skill
Stars: 0Claude CodeCodexTriage a decision letter and build a point-by-point response and revision plan. Use when reviews have come back — major or minor revision, reject-and-resubmit, or a rejection worth appealing — and the author must decide what to concede, what to contest, and in what order to revise. Covers reading the editor's letter for what it actually asks, separating reviewer requests by cost and merit, response-letter structure, and the rhetoric of disagreeing without antagonizing. Do not use for the pre-submission audit; that is `core/audit-manuscript/SKILL.md`.
angushushu/shu-academic-writing-skill
Stars: 0Claude CodeCodex当用户需要把内容(文章、笔记、截图、数据、产品说明)做成中文图文卡片组图时使用——小红书 / Rednote 3:4 竖图、公众号封面、社交卡。提供三套独家视觉语言(静纸 Still Paper本手记 / Signal Proof 证据层 / Bridge Canvas 跨平台桥),由 Claude 读懂内容、自己撰写 brief.json,交给确定性引擎渲染出第一眼惊艳、一眼可辨、国内开箱即用的图文组图。
dososo/blcaptain-style-skill
Stars: 187Claude CodeCodexGenerate leftover PlantUML types Mermaid cannot do easily (Salt wireframes, use case, timing, ArchiMate, nwdiag, WBS) and convert them to PNG/SVG. Use when asked for a wireframe, PlantUML image export, extract puml from markdown, or prepare Confluence uploads. Class, ER, state, sequence, and C4 default to design-doc-mermaid on GitHub wiki.
SpillwaveSolutions/plantuml
Stars: 61Claude CodeCodexDesign, implement, and review modern C++ APIs and native implementation code. Use when working on .cpp, .hpp, CMake, RAII ownership, std::variant, callbacks, async work, platform bridges, or C++-backed React Native Nitro Module implementations.
jonluca/palate
Stars: 4Claude CodeCodexThePrimeagen/99
Stars: 4.7kClaude CodeCodexThePrimeagen/99
Stars: 4.7kClaude CodeCodexThePrimeagen/99
Stars: 4.7kClaude CodeCodexThePrimeagen/99
Stars: 4.7kClaude CodeCodexA relentless interview to sharpen a plan or design.
gentleeduck/duck-sqllsp
Stars: 3Claude CodeCodexStop. That last message did not land: re-pitch it.
gentleeduck/duck-sqllsp
Stars: 3Claude CodeCodexUse when detecting release semver version drift across VERSION, GEMINI.md, and package.json, maintaining CHANGELOG and README release hygiene, or atomically bumping release versions
Snoozer10/synthesize-skills
Stars: 0Claude CodeCodexUse when checking code changes for orphaned callers, outdated tests, or stale documentation, discovering change blast radius, or verifying git staged parity against the dependency registry
Snoozer10/synthesize-skills
Stars: 0Claude CodeCodexUse when extracting codebase standards, response envelopes, and error codes via AST, checking architectural compliance, indexing symbols, shaping specs with rich semantic assertions, or verifying contracts in specs directory
Snoozer10/synthesize-skills
Stars: 0Claude CodeCodexUse when detecting release semver version drift across VERSION, GEMINI.md, and package.json, maintaining CHANGELOG and README release hygiene, or atomically bumping release versions
Snoozer10/synthesize-skills
Stars: 0Claude CodeCodexUse when checking code changes for orphaned callers, outdated tests, or stale documentation, discovering change blast radius, or verifying git staged parity against the dependency registry
Snoozer10/synthesize-skills
Stars: 0Claude CodeCodexUse when extracting codebase standards, response envelopes, and error codes via AST, checking architectural compliance, indexing symbols, shaping specs with rich semantic assertions, or verifying contracts in specs directory
Snoozer10/synthesize-skills
Stars: 0Claude CodeCodexGolang benchmarking, profiling, and performance measurement. Use when writing, running, or comparing Go benchmarks, profiling hot paths with pprof, interpreting CPU/memory/trace profiles, analyzing results with benchstat, setting up CI benchmark regression detection, or investigating production performance with Prometheus runtime metrics. Also use when the developer needs deep analysis on a specific performance indicator - this skill provides the measurement methodology, while `samber/cc-skills-golang@golang-performance` provides the optimization patterns.
EmanuProds/dotfiles
Stars: 0Claude CodeCodexGolang CLI application development. Use when building, modifying, or reviewing a Go CLI tool — especially for command structure, flag handling, configuration layering, version embedding, exit codes, I/O patterns, signal handling, shell completion, argument validation, and CLI unit testing. Also triggers when code uses cobra, viper, or urfave/cli. For cobra-specific APIs → See `samber/cc-skills-golang@golang-spf13-cobra` skill; for viper configuration layering → See `samber/cc-skills-golang@golang-spf13-viper` skill.
EmanuProds/dotfiles
Stars: 0Claude CodeCodexGolang code style conventions — line length and breaking, variable declarations, control flow clarity, when comments help vs hurt. Use when writing or reviewing Go code, asking about style or clarity, or establishing project coding standards. Not for naming conventions (→ See `samber/cc-skills-golang@golang-naming` skill), linter configuration (→ See `samber/cc-skills-golang@golang-lint` skill), or doc comments (→ See `samber/cc-skills-golang@golang-documentation` skill).
EmanuProds/dotfiles
Stars: 0Claude CodeCodexGolang concurrency design — goroutine lifecycle and leak prevention, channels and `select`, channel ownership and direction, `sync.Mutex`/`RWMutex`/`sync.Map`/`sync.Once`/atomics, `errgroup`, `singleflight`, worker pools, and fan-out/fan-in pipelines. Use when writing or reviewing concurrent Go code, when choosing between channels and mutexes, when protecting a shared map or counter, or when a goroutine has no clear exit. Not for defensive coding unrelated to concurrency such as nil panics, slice aliasing, or numeric overflow (→ See `samber/cc-skills-golang@golang-safety` skill), and not for debugging a specific hung, crashing, or racing program after the fact (→ See `samber/cc-skills-golang@golang-troubleshooting` skill).
EmanuProds/dotfiles
Stars: 0Claude CodeCodexIdiomatic context.Context usage in Golang — propagation through API boundaries, cancellation, timeouts and deadlines, request-scoped values, context.WithoutCancel for background work outliving requests. Apply when designing context propagation across layers, debugging leaked or unexpired contexts, choosing between context.Background/TODO/WithoutCancel, or storing values in context. Not for code that merely accepts ctx as first parameter.
EmanuProds/dotfiles
Stars: 0Claude CodeCodexGolang data structures — slices (internals, capacity growth, preallocation, slices package), maps (internals, hash buckets, maps package), arrays, container/list/heap/ring, strings.Builder vs bytes.Buffer, generic collections, pointers (unsafe.Pointer, weak.Pointer), and copy semantics. Use when choosing or optimizing Go data structures, implementing generic containers, using container/ packages, unsafe or weak pointers, or questioning slice/map internals. Not for applying optimization patterns once profiling has identified a bottleneck (→ See `samber/cc-skills-golang@golang-performance` skill).
EmanuProds/dotfiles
Stars: 0Claude CodeCodexComprehensive guide for Go database access — parameterized queries, struct scanning, NULLable columns, transactions, isolation levels, SELECT FOR UPDATE, connection pool, batch processing, context propagation, and migration tooling. Use when writing, reviewing, or debugging Golang code that interacts with PostgreSQL, MariaDB, MySQL, or SQLite; for database testing; or for questions about database/sql, sqlx, or pgx. Does NOT generate database schemas or migration SQL.
EmanuProds/dotfiles
Stars: 0Claude CodeCodexDependency management for Golang projects — go.mod and go.sum, `go get` install and upgrade flows, Minimal Version Selection, conflict resolution with replace/exclude/retract, `govulncheck` scanning of the module tree, outdated dependency and binary size auditing, vendoring, `tool` directives, and go.work workspaces. Use when adding, removing, or upgrading Go dependencies, deciding whether to take on a package, resolving version conflicts, or auditing what a module pulls in. Covers choosing and upgrading dependency versions, not the surrounding tooling: do NOT use for fixing an exploitable vulnerability in code (→ See `samber/cc-skills-golang@golang-security` skill) or for wiring Dependabot/Renovate update bots into CI workflows (→ See `samber/cc-skills-golang@golang-continuous-integration` skill).
EmanuProds/dotfiles
Stars: 0Claude CodeCodex