Explore skills
Showing 48661–48690 of 77104 skills
Diagnose 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 CodeCodexDirect PubMed and NCBI E-utilities search workflows for biomedical literature, MeSH queries, PMID lookup, citation retrieval, and API-backed literature monitoring.
sakamoto-family-smile/agent_monorepo
Stars: 0Claude CodeCodexUSPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
sakamoto-family-smile/agent_monorepo
Stars: 0Claude CodeCodexgget CLI and Python workflow for quick genomic database queries, sequence lookup, BLAST-style searches, enrichment checks, and reproducible bioinformatics evidence logs.
sakamoto-family-smile/agent_monorepo
Stars: 0Claude CodeCodexSystematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
sakamoto-family-smile/agent_monorepo
Stars: 0Claude CodeCodexStructured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
sakamoto-family-smile/agent_monorepo
Stars: 0Claude 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 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 CodeCodexIdiomatic Golang design patterns — functional options, constructor APIs, `init()` and global-state avoidance, enums, panic vs error decisions, resource management and lifecycle, graceful shutdown, timeouts and retries, streaming and iterators, and architecture styles (clean, hexagonal, DDD, flat). Apply when choosing between architectural patterns, implementing functional options, designing constructor APIs, setting up graceful shutdown, applying resilience patterns, or asking which idiomatic Go pattern fits a specific problem. Not for wiring a DI container or comparing DI libraries (→ See `samber/cc-skills-golang@golang-dependency-injection` skill), nor for error wrapping, `errors.Is`/`As`, or logging mechanics (→ See `samber/cc-skills-golang@golang-error-handling` skill).
EmanuProds/dotfiles
Stars: 0Claude CodeCodexCompile-time dependency injection in Golang using google/wire — wire.NewSet, wire.Build, wire.Bind (interface→concrete), wire.Struct, wire.Value, wire.InterfaceValue, wire.FieldsOf, cleanup functions, //go:build wireinject injector files, and generated wire_gen.go. Apply when using or adopting google/wire, when the codebase imports `github.com/google/wire`, or when wiring an application graph at compile time via `wire.Build`. For runtime DI with reflection, see `samber/cc-skills-golang@golang-uber-dig` skill.
EmanuProds/dotfiles
Stars: 0Claude CodeCodexProvides gRPC usage guidelines, protobuf organization, and production-ready patterns for Golang microservices. Use when implementing, reviewing, or debugging gRPC servers/clients, writing proto files, setting up interceptors, handling gRPC errors with status codes, configuring TLS/mTLS, testing with bufconn, or working with streaming RPCs.
EmanuProds/dotfiles
Stars: 0Claude CodeCodexLinting best practices and golangci-lint configuration for Golang projects — running linters, configuring .golangci.yml, suppressing warnings with nolint directives, interpreting lint output, and selecting linters. Use when configuring golangci-lint, asking about lint warnings or nolint suppressions, setting up code quality tooling, or choosing linters. Also use when the user mentions golangci-lint, go vet, staticcheck, or revive. Not for wiring a lint step into a GitHub Actions pipeline (→ See `samber/cc-skills-golang@golang-continuous-integration` skill).
EmanuProds/dotfiles
Stars: 0Claude CodeCodexModernize Golang code to use recent language features, standard library improvements, and idiomatic patterns. Use when reviewing Go code with old-style patterns, when encountering a deprecation warning, or when the user asks for modernization, a Go version upgrade (e.g. to Go 1.27), or a CI/tooling refresh. Not for structural refactors, extracting functions, or moving code between packages (→ See `samber/cc-skills-golang@golang-refactoring` skill).
EmanuProds/dotfiles
Stars: 0Claude CodeCodex