Loading...
Loading...
Found 78 Skills
Own rendered visuals and visual redesign from supplied content or values: plot, beautify, lay out, generate, reconstruct, and QA paper figures, visual tables, method/architecture diagrams, icons, palettes, reference-guided layout control, and editable SVG/PDF/PPTX. Use for result-table layout, color/readability improvement, visual table redesign without changing numbers, 绘图美化, 排版, 配色, architecture diagrams, GPT Image 2 generation, reference-driven composition, explicit pure SVG, and editable reconstruction. Visual beautification remains here even for experiment results. Do not choose datasets/baselines/metrics, design evidence semantics, invent content, review the paper, rewrite prose, or convert PDFs into writing exemplars.
Testing reference for Megatron Bridge — unit and functional test layout, tier semantics (L0/L1/L2/flaky), script conventions, running tests locally, adding/moving/disabling tests, and pytest conventions.
Guide to Business Semantics and Fact Judgment for Qiqi Service Industry ERP. It is used when you need to understand product capability domains, archives, documents, master-detail tables, project-based business-finance stages, statuses, references, enumerations, and time semantics, calibrate profit, budget, task or working hour calibers, or judge whether records can support a certain business conclusion.
REST API design and development expert specializing in endpoint design, HTTP semantics, versioning, error handling, pagination, and OpenAPI documentation. Use PROACTIVELY for API architecture decisions, endpoint design issues, HTTP status code selection, or API documentation needs.
Design how an API platform communicates status and incidents to external consumers - status-page modeling (the four-stage incident lifecycle, degraded/partial/major component semantics, component granularity), monitoring-driven status instead of a hand-flipped green light, pull and push channels, incident-update cadence and templates, public postmortems for a developer audience, public SLA/SLO reporting, and maintenance-window notices. Use whenever the user mentions a status page, Statuspage, incident updates, uptime or SLA reporting, postmortems, or scheduled maintenance - even if they never say "status communication". Do NOT use for deprecation and breaking-change notices - use samber/developer-platform-skills@api-versioning-policy instead.
Blocks destructive git and filesystem commands before execution. Prevents accidental loss of uncommitted work from git checkout --, git reset --hard, rm -rf, and similar destructive operations. Works as a Claude Code PreToolUse hook with fail-open semantics.
Use with root `twg` for Jira workitems, similar issue discovery, duplicate detection, projects, boards, sprints, fields, transitions, comments, links, and administration. Applies Jira semantics and safe mutation rules.
Use this skill when validating ANY potential code review finding. Apply BEFORE classifying to verify the finding is real; can you trace incorrect behavior, is it handled elsewhere, and are you certain about framework semantics? If any answer is no, DO NOT create the finding.
Guides creation and modification of ASP.NET Core Web API endpoints with correct HTTP semantics, OpenAPI metadata, and error handling. USE FOR: adding new API endpoints (controllers or minimal APIs), wiring up OpenAPI/Swagger, creating .http test files, setting up global error handling middleware. DO NOT USE FOR: general C# coding style, EF Core data access or query optimization (use optimizing-ef-core-queries), frontend/Blazor work, gRPC services, or SignalR hubs.
Converts any Claude Code skills repository into an official plugin marketplace. Analyzes existing skills, generates .claude-plugin/marketplace.json conforming to the Anthropic spec, validates with `claude plugin validate`, tests real installation, and creates a PR to the upstream repo. Encodes hard-won anti-patterns from real marketplace development (schema traps, version semantics, description pitfalls). Use when the user mentions: marketplace, plugin support, one-click install, marketplace.json, plugin distribution, auto-update, or wants a skills repo installable via `claude plugin install`. Also trigger when the user has a skills repo and asks about packaging, distribution, or making it installable.
Design or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.
Review REST API contracts for HTTP semantics, versioning, backward compatibility, and response consistency. Use when user asks "review API", "check endpoints", "REST review", or before releasing API changes.