6.8K skills · sorted by relevance
Plan user research by matching methods to study goals and explaining participant numbers and confidence. Synthesize tagged observations into recurring findings, distinguish isolated anecdotes, and organize evidence so research results can be found and reused.
Design service monitoring with Prometheus, write PromQL queries to analyze metrics, and build Grafana dashboards. Configure actionable alerts and manage metric labels so monitoring stays useful as the volume of collected data grows.
Analyze Solidity smart contracts with Slither and Mythril before Ethereum deployment. Combine code inspection with execution path analysis, review potential vulnerabilities, remove duplicate findings, and produce an audit report with severity ratings and suggested fixes.
Compare the installed Claude Code version with release notes and recent bug reports to decide whether to stay, update, or use a specific version. Recommendations account for reported problems, relevant fixes, and how Claude Code was installed.
Compares PIA/DPIA methodologies: CNIL PIA tool, ICO DPIA template, NIST Privacy Framework, and ISO 29134. Provides methodology selection criteria based on regulatory jurisdiction, organisation maturity, processing complexity, and resource availability. Covers regulatory acceptance, tool features, and cross-methodology mapping. Keywords: PIA methodology, CNIL, ICO, NIST Privacy Framework, ISO 29134, DPIA comparison, assessment.
The English summary is being prepared. Showing the original description.
Interact with Ethereum and EVM blockchains using ethers.js. Use when a user asks to connect to Ethereum, read blockchain data, send transactions, interact with smart contracts, or build a dApp frontend.
The English summary is being prepared. Showing the original description.
"Design and conduct mixed methods research using convergent, explanatory sequential, or exploratory sequential strategies with genuine integration of qualitative and quantitative strands. Use this skill when the user needs to choose a mixed methods design, integrate qualitative and quantitative data at design, methods, or interpretation levels, justify mixing on pragmatist grounds, or when they ask 'which mixed methods design should I use', 'how do I integrate qual and quant findings', or 'is running both qual and quant enough to be mixed methods'.".
The English summary is being prepared. Showing the original description.
Use when a task needs the judgment of a Continuous Mining Machine Operator in underground coal — reading a methane monitor trend and deciding whether to de-energize, judging whether cumulative unbolted advance has hit the roof control plan's cut-depth limit, deciding whether a permissibility defect requires immediate shutdown in a gassy heading, diagnosing whether a shift's production shortfall traces to cutting rate or shuttle-car haulage, or deciding whether a "drummy" roof sound stops the cut.
The English summary is being prepared. Showing the original description.
Generate publication-ready methods sections, figure legends, supplementary tables, and data availability statements from ENCODE analysis provenance. Implements the scientific documentation standards requiring complete metadata reporting. Use when the user needs to write methods, generate figure legends, create supplementary tables, draft data availability statements, compile tool citations, or auto-generate any publication text from their ENCODE analysis. Trigger on: methods section, figure legend, supplementary table, data availability, tool citations, publication writing, manuscript, write methods, methods draft, write up, write-up, paper writing, reproducible methods.
The English summary is being prepared. Showing the original description.
Plan, execute, and document validation, verification, and transfer of analytical procedures under the governing framework - ICH Q2(R2) and Q14, USP <1220>/<1225>/<1226>, ICH M10 bioanalytical, CLSI EP, or ISO/IEC 17025. Use for HPLC, LC-MS/MS, GC, CE, ICP-MS, dissolution, qNMR, qPCR, NIR, and ligand binding or cell-based assays whenever the question is whether a procedure is fit for its intended purpose. Triggers include "method validation", "analytical method validation", "AMV", "validation protocol", "acceptance criteria", "linearity", "reportable range", "accuracy and precision", "repeatability", "intermediate precision", "recovery", "LOD", "LOQ", "detection limit", "quantitation limit", "specificity", "robustness", "method transfer", "method comparison", "Deming", "Passing-Bablok", "Bland-Altman", "equivalence testing", "OOS investigation", "ICH Q2", "Q2(R2)", "Q14", "USP 1225", "ICH M10", "incurred sample reanalysis", "ISR", "CLSI EP", and any request to show that an assay works.
The English summary is being prepared. Showing the original description.
지역 변수가 서로 얽혀 Extract Method가 불가능한 거대 메서드를 별도 클래스(Method Object)로 추출. "긴 메서드를 클래스로", "지역 변수 때문에 추출 불가", "method object", "/extract-method-object" 요청 시 사용. 단, 지역 변수 얽힘 없이 잘라낼 수 있는 긴 메서드는 /intent-revealing-names(grouping→extract)가 적합. /extract-method-object [commit-ref]로 호출.
The English summary is being prepared. Showing the original description.
Plan, execute, and document validation, verification, and transfer of analytical procedures under the governing framework - ICH Q2(R2) and Q14, USP <1220>/<1225>/<1226>, ICH M10 bioanalytical, CLSI EP, or ISO/IEC 17025. Use for HPLC, LC-MS/MS, GC, CE, ICP-MS, dissolution, qNMR, qPCR, NIR, and ligand binding or cell-based assays whenever the question is whether a procedure is fit for its intended purpose. Triggers include "method validation", "analytical method validation", "AMV", "validation protocol", "acceptance criteria", "linearity", "reportable range", "accuracy and precision", "repeatability", "intermediate precision", "recovery", "LOD", "LOQ", "detection limit", "quantitation limit", "specificity", "robustness", "method transfer", "method comparison", "Deming", "Passing-Bablok", "Bland-Altman", "equivalence testing", "OOS investigation", "ICH Q2", "Q2(R2)", "Q14", "USP 1225", "ICH M10", "incurred sample reanalysis", "ISR", "CLSI EP", and any request to show that an assay works.
The English summary is being prepared. Showing the original description.
Locate CCSCustomHudLayout_SetHasClass in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CCSCustomHudLayout_SetHasClass" (symbol CCSCustomHudLayout_SetHasClass). The gamedata consumer stores a BYTE SIGNATURE for this entry - ALWAYS emit the func schema (func_sig), never vfunc fields. The function may be virtual; locating it via the owning class vtable (RTTI) is a fine strategy, but once found, read its head bytes and emit func_sig. Locate via cross-references, distinctive constants/strings, callers of related symbols, or vtable slots; verify by decompilation before committing. Trigger: CCSCustomHudLayout_SetHasClass, CCSCustomHudLayout_SetHasClass
The English summary is being prepared. Showing the original description.
Locate CCSCustomHudLayout_SetHasClassForPlayer in CS2 server.dll / libserver.so via IDA Pro MCP and emit a fresh, minimal-unique signature or offset for the local gamedata entry "CCSCustomHudLayout_SetHasClassForPlayer" (symbol CCSCustomHudLayout_SetHasClassForPlayer). The gamedata consumer stores a BYTE SIGNATURE for this entry - ALWAYS emit the func schema (func_sig), never vfunc fields. The function may be virtual; locating it via the owning class vtable (RTTI) is a fine strategy, but once found, read its head bytes and emit func_sig. Locate via cross-references, distinctive constants/strings, callers of related symbols, or vtable slots; verify by decompilation before committing. Trigger: CCSCustomHudLayout_SetHasClassForPlayer, CCSCustomHudLayout_SetHasClassForPlayer
The English summary is being prepared. Showing the original description.
Swap or trade tokens on Base network. Use when you or the user want to trade, swap, exchange, buy, sell, or convert between tokens like USDC, ETH, and WETH. Covers phrases like "buy ETH", "sell ETH for USDC", "convert USDC to ETH", "get some ETH".
The English summary is being prepared. Showing the original description.
Reviews papers, research proposals, and literature reviews using a consistent scoring guide. Examines methods, evidence, citations, and writing, then separates serious problems from revision suggestions and identifies concrete next edits.
Simulate readers encountering a draft for the first time to see whether they open it, where their attention fades, and what they remember. Receive reader comments alongside the text without rewrites or suggested fixes.
Review JavaScript loops and replace suitable ones with standard array and object methods. Make transformations, filtering, and aggregation easier to understand, with practical explanations and browser checks to confirm that changes preserve the intended behavior.
Prepare constructive review drafts for scientific manuscripts, protocols, preprints, and proposals. Organize checks of claims, evidence, methods, statistics, reproducibility, ethics, figures, and citations into specific comments that a responsible human reviewer can verify and revise.
Define service reliability measurements and targets, then turn them into Prometheus monitoring rules and alerts. Calculate error budgets, the amount of failure allowed, and outline Grafana dashboards for tracking reliability and deciding when to prioritize fixes.
Check Microsoft API usage against official documentation and code samples. Find methods, parameters, and packages for Azure SDKs, .NET libraries, and Microsoft APIs, then compare implementations to investigate errors or outdated patterns.
Build a pair trading strategy for two related instruments using their price ratio. Measure how far the ratio moves from its recent average, generate opposite buying and selling signals, and close positions when the ratio returns near that average.
Review an analysis before sharing it with stakeholders. Check calculations, data selection, comparison methods, potential bias, charts, and whether conclusions follow from the evidence, then receive a readiness assessment and specific improvements.
Build market research evidence by comparing two market-size estimates, calculating survey sample sizes for each customer group, and scoring potential segments. Outputs show methods and assumptions so teams can assess the basis for business decisions.