Loading...
Loading...
Found 6,275 Skills
gget CLI and Python workflow for quick genomic database queries, sequence lookup, BLAST-style searches, enrichment checks, and reproducible bioinformatics evidence logs.
Build persistent multi-agent operating systems on Claude Code. Covers kernel architecture, specialist agents, slash commands, file-based memory, scheduled automation, and state management without external databases.
Personal financial planning framework for China / HK / Singapore investors via Longbridge — retirement savings targets (based on current Longbridge account net worth), education fund planning, balance sheet review, cash flow analysis, gap analysis between current portfolio and financial goals. Triggers: "财务规划", "退休规划", "储蓄目标", "教育金", "资产负债表", "财富规划", "财务目标", "个人理财", "財務規劃", "退休規劃", "儲蓄目標", "教育金", "資產負債表", "財富規劃", "財務目標", "個人理財", "financial planning", "retirement planning", "savings goal", "education fund", "personal finance", "wealth planning", "net worth", "financial goals", "balance sheet", "gap analysis".
Guides structured security log analysis across authentication, network, endpoint, and cloud audit log sources. Auto-invoked when the user shares log data, asks about suspicious events, needs help interpreting Windows Event IDs or Linux auth logs, or is establishing baselines for anomaly detection. Produces log source taxonomy, anomaly identification, baseline recommendations, and correlation findings mapped to MITRE ATT&CK v16 techniques.
Assists with CachyOS and Arch-based Linux tasks: running commands, writing scripts, system diagnosis, and troubleshooting. Use when the user asks about CachyOS, Arch Linux, pacman, kernel (BORE/EEVDF/BMQ), systemd, performance tuning, package management, shell scripts, or Linux administration.
Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets. Supports Base through agentwallet-sdk and X Layer through OKX Payments / OKX Agent Payments Protocol.
Guides secure software delivery and DevSecOps for cleared/classified or high-side programs—disconnected or air-gapped CI/CD, artifact promotion across classification boundaries (conceptual), SBOM/signing/ provenance, SAST/DAST/secrets/IaC/container gates, supply-chain controls, STIG/CIS deploy baselines, IaC for classified landing zones, cleared developer workstations, build/deploy audit logging, and ATO/RMF pipeline evidence (not SSP ownership). Use for classified DevSecOps, cleared pipeline, high-side CI/CD, air-gapped build, cross-domain release, classified software delivery, STIG pipeline, ATO evidence CI, SBOM classified, secure software factory—not portfolio cyber governance (classified-cyber-security-senior-manager), ISSO/SSP (information-systems-security-officer-classified-specialist), commercial-only DevSecOps (devsecops), general DevOps (devops), build-only validation (build-validator), pentest (penetration-tester), or enterprise GRC-only (compliance-specialist).
A qualitative research assistant tool based on Braun & Clarke's Reflexive Thematic Analysis framework. Supports two input modes: (1) Provide raw interview text directly → The skill completes initial TA coding for each document, then proceeds to theme identification after summarization; (2) Provide existing initial coding pool → Directly enter the process of clustering, review, and naming suggestions. Outputs a structured candidate theme table, clearly marking codes with ambiguous boundaries and naming suggestions to be decided by researchers. This skill is triggered when users mention terms such as "thematic analysis", "theme coding", "help me cluster codes", "extract themes from codes", "Braun Clarke", "candidate themes", "how to categorize these codes into themes", "help me check the theme structure", "conduct thematic analysis on interviews". Note the difference from grounded-coding: grounded-coding focuses on category construction and theoretical relationships for procedural grounded theory; thematic-analysis focuses on semantic theme identification following the Braun & Clarke approach, outputting theme structures rather than theoretical propositions.
Best practices for contributing code to TensorRT-LLM. Covers the official contribution process (issue tracking, fork workflow, DCO signing), coding guidelines, implementation workflow, common mistakes, testing strategy, commit hygiene, and review readiness. Incorporates rules from CONTRIBUTING.md and CODING_GUIDELINES.md plus lessons distilled from real PR retrospectives. Use when implementing new features, optimizations, or bug fixes in the TensorRT-LLM codebase.
Performance review and testing: evaluate Core Web Vitals, page load times, bundle sizes, runtime performance, resource optimization, and rendering efficiency with browser-based measurement and benchmarking.
Use this skill when the user asks about Goldsky Subgraphs — deploying, managing, or querying subgraphs. Triggers on: 'deploy a subgraph', 'migrate from The Graph', 'what is a subgraph', 'GraphQL endpoint', 'low-code or no-code subgraph', 'subgraph tags', 'subgraph webhooks', 'cross-chain subgraph', 'subgraph stalled', 'subgraph API key', 'init subgraph', 'scaffold subgraph', 'subgraph logs', 'pause subgraph', 'start subgraph', 'graft subgraph'. Also use this skill when the user wants to build a GraphQL API over onchain data, power a dApp frontend with indexed blockchain data, or reuse an existing TheGraph subgraph on Goldsky. For questions about streaming raw chain data directly to a database without GraphQL, use the turbo-builder or mirror skills instead.
Use this skill when the user asks about Goldsky Edge — the managed RPC endpoint service for EVM chains. Triggers on: 'Edge RPC', 'Goldsky RPC endpoint', 'edge.goldsky.com', 'eth_getLogs is slow', 'RPC rate limit', 'hedged requests', 'flashblocks', 'HyperEVM system transactions', 'x402 pay-per-request RPC', 'Goldsky Edge pricing', 'Edge dashboard', 'gs_edge_ API key', 'rpc-edge'. Also use this skill when the user wants a resilient, low-latency JSON-RPC endpoint for EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon zkEVM, BSC, Avalanche, Berachain, HyperEVM, Monad, Sei, Sonic, Unichain, zkSync, etc.), is debugging RPC errors like -32005/-32012/-32014/-32015/-32016, or is comparing providers (Alchemy, Infura, QuickNode, Ankr) against Edge. For questions about self-hosting eRPC or custom eRPC configuration beyond what Edge exposes, point them at https://docs.erpc.cloud/llms.txt. Do NOT trigger on Goldsky Mirror, Turbo, or Subgraph pipeline questions — those belong to their respective skills.