Loading...
Loading...
Found 1,907 Skills
Test C# MCP servers at multiple levels: unit tests for individual tools and integration tests using the MCP client SDK. USE FOR: unit testing MCP tool methods, integration testing with in-memory MCP client/server, end-to-end testing via MCP protocol, testing HTTP MCP servers with WebApplicationFactory, mocking dependencies in tool tests, creating evaluations for MCP servers, writing eval questions, measuring tool quality. DO NOT USE FOR: testing MCP clients (this is server testing only), load or performance testing, testing non-.NET MCP servers, debugging server issues (use mcp-csharp-debug).
Use when the user wants to iterate on a viral-article scoring system itself, calibrate or improve a scoring prompt against labeled samples, or run batch scoring experiments on a fixed article set. Best for prompt-only scoring research where the evaluator scripts stay fixed and only the scoring rubric/prompt is meant to evolve.
You must use this when critiquing academic manuscripts, evaluating methodological rigor, or providing structured reviewer feedback.
Fast DataFrame library (Apache Arrow). Select, filter, group_by, joins, lazy evaluation, CSV/Parquet I/O, expression API, for high-performance data analysis workflows.
Market intelligence, competitive analysis, technical evaluations, and technology decisions. Use when researching companies, analyzing competitors, evaluating frameworks, or making tech stack decisions.
Build a structured taxonomy of failure modes from open-coded trace annotations. Use this skill whenever the user has freeform annotations from reviewing LLM traces and wants to cluster them into a coherent, non-overlapping set of binary failure categories (axial coding). Also use when the user mentions "failure modes", "error taxonomy", "axial coding", "cluster annotations", "categorize errors", "failure analysis", or wants to go from raw observation notes to structured evaluation criteria. This skill covers the full pipeline: grouping open codes, defining failure modes, re-labeling traces, and quantifying error rates.
Advisory fee billing: fee calculation (tiered, flat, breakpoint), billing cycles, AUM valuation, direct-debit/invoice collection, GAAP revenue recognition, ADV Part 2A/Reg BI/ERISA 408(b)(2) disclosure, billing exceptions, system migration, revenue forecasting, concentration analysis.
MantaBase T3 Hardware Audit System (Chinese Version). Objectively classify hardware products based on design theories through Brand Blinding, three Auditor (Tool/Toy/Trash) special scoring and Peer Review. Triggers: product link, T3 audit, Tool/Toy/Trash classification, hardware evaluation, VC investment advice
Run verification checks for a task and evaluate results. Use when the user wants to verify a task's acceptance criteria.
Expert at analyzing the quality and effectiveness of Claude Code components (agents, skills, commands, hooks). Assumes component is already technically valid. Evaluates description clarity, tool permissions, auto-invoke triggers, security, and usability to provide quality scores and improvement suggestions.
Retrieve analyst financial estimates including Revenue and EPS projections with low/high ranges and analyst coverage. Use when analyzing forward expectations, consensus estimates, valuation inputs, or comparing projections to historical performance.
Initiating-coverage report framework — five-step workflow to generate an institutional-grade coverage initiation report: ① company overview ② industry positioning ③ financial modelling ④ valuation analysis ⑤ investment conclusion. Covers business description, competitive advantages, financial health, valuation multiples, price target, and risk factors. Triggers: "首次覆盖", "初始覆盖", "覆盖报告", "研报框架", "投资报告", "建立覆盖", "首次評級", "初始覆蓋", "覆蓋報告", "建立覆蓋", "initiate coverage", "coverage initiation", "first coverage", "equity research report", "investment report", "initiating coverage", "research initiation", "NVDA initiate coverage".