Write variance commentary for A-share financial results. Adapts the original variance-commentary skill for Chinese financial statements, CAS conventions, and Chinese business terminology. Triggers on "A股业绩点评", "财报点评", "variance commentary China", "业绩分析", "variances [company]", or "commentary on [company] results".
日本語の概要は準備中です。原文の説明を表示しています。
jwangkun/claude-for-financial-services-cn☆ 8332026年9月14日 更新
When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum.
日本語の概要は準備中です。原文の説明を表示しています。
AvdLee/RocketSimApp☆ 8062026年10月14日 更新
Review Java concurrency code for thread safety, race conditions, deadlocks, and modern patterns (Virtual Threads, CompletableFuture, @Async). Use when user asks "check thread safety", "concurrency review", "async code review", or when reviewing multi-threaded code.
日本語の概要は準備中です。原文の説明を表示しています。
decebals/claude-code-java☆ 7502026年9月7日 更新
Define a brand's target audience with deep personas, psychographics, and ICP (Ideal Customer Profile). Use when the user says "target audience", "ideal customer", "customer persona", "audience persona", "ICP", "who is our customer", "define our audience", "audience research", "buyer persona", "who should we be targeting", "audience profile", "customer profile", "who buys this", or needs to understand their audience more deeply before investing in brand or marketing work.
日本語の概要は準備中です。原文の説明を表示しています。
arnabbagxd/Brand-building-skills☆ 7442026年6月13日 更新
Writes, improves, or rewrites Seedance 2.0 prompts that TRANSFORM footage the user already has (video-to-video), rather than building a scene from scratch. Use whenever a real clip is the starting point and they want to: add a VFX element (set a head or hair on fire, transform a hand, make a limb invisible), swap the environment around a preserved subject (desert, clouds, lava, a neon city), drop a giant photoreal creature behind or onto a subject/landmark, relight or regrade so subject and added elements read as one shot, sync a crash-zoom or push-in to a spoken line or timecode, or generate a matching transformed start frame to animate from. Also use when they paste such a prompt and ask to change its lighting, timing, creature, or runtime, or say 'make a Seedance prompt for this video' with a clip attached. This is the video-to-video specialization; for a brand-new scene from image references with no source clip to preserve, higgsfield-seedance applies instead.
日本語の概要は準備中です。原文の説明を表示しています。
OSideMedia/higgsfield-ai-prompt-skill☆ 7402026年9月27日 更新
Write an email drip sequence for affiliate marketing. Triggers on: "write me an email sequence", "create a drip campaign", "email nurture sequence", "affiliate email funnel", "welcome email series", "email onboarding sequence", "write emails for my list", "set up a drip sequence", "email campaign for [product]", "nurture my subscribers", "email follow-up sequence", "build my email funnel", "write 5 emails promoting [product]", "email automation sequence".
日本語の概要は準備中です。原文の説明を表示しています。
Affitor/affiliate-skills☆ 7102026年10月13日 更新
Dung khi thue NGUOI NGOAI lam — agency, freelancer, production house, vendor: scope of work, spec deliverable, so vong sua, quy trinh duyet, moc thanh toan, dieu khoan IP va bao mat, bang danh gia vendor sau du an. Kich hoat khi user nhac 'brief agency', 'thue freelancer', 'quan ly vendor', 'scope of work', 'agency lam khong dung y', 'thue ngoai quay TVC', 'bao gia agency co hop ly khong', 'onboard vendor moi'. Khong dung cho — giao viec cho nhan su noi bo thi dung skill 64-team-brief; brief creator quay UGC hoac KOC thi dung skill 06-brief-ugc-egc; nhan brief tu khach khi CHINH MINH la agency thi dung skill 20-brief-client-intake.
日本語の概要は準備中です。原文の説明を表示しています。
minhnv0807/ai-business-skills☆ 6132026年9月12日 更新
Use when a leader assigns work to a marketing team member or runs a cross-functional meeting — a task brief with concrete deliverables, a deadline with time and timezone, a definition of done, constraints, and check-in points, plus an async-first meeting agenda and action-item template. Trigger on 'assign a task', 'brief for my team', 'team brief', 'definition of done', 'meeting agenda template', 'my team keeps delivering the wrong thing'. Also use when the user says nobody knows who owns what. Not for — the campaign brief the whole team executes from, see `02-campaign-brief-global`; briefing an external agency or freelancer, see `67-agency-vendor-brief-global`; evaluating performance, see `65-team-performance-review-global`.
日本語の概要は準備中です。原文の説明を表示しています。
minhnv0807/ai-business-skills☆ 6132026年9月12日 更新
Your launch lead. Builds a dated, step-by-step launch plan: a cheap real-world test first (a waitlist, a pre-sale or a pop-up with a real price, so real buyers confirm what the simulated panel said), then the countdown to opening day with owners and deadlines, the launch-day run sheet, and the first 30 days of what to measure and what to change. Use when the user says "how do I launch", "launch plan", "when can I open", "launch checklist", "go live", or "soft open".
日本語の概要は準備中です。原文の説明を表示しています。
Jakeschincariol/founder-skill☆ 5892026年10月7日 更新
Implement modern concurrency with Virtual Threads and Structured Concurrency in Java. Use when implementing Java Virtual Threads (Java 21), Structured Concurrency with StructuredTaskScope, CompletableFuture pipelines, or debugging race conditions.
日本語の概要は準備中です。原文の説明を表示しています。
HoangNguyen0403/agent-skills-standard☆ 5752026年10月12日 更新
Train or fine-tune SentenceTransformer bi-encoders, CrossEncoder rerankers, or SparseEncoder models, including losses, negatives, evaluation, distillation, LoRA, and Matryoshka. Use for sentence-transformers training tasks.
日本語の概要は準備中です。原文の説明を表示しています。
waybarrios/opencode-power-pack☆ 5382026年10月12日 更新
Use when you need to design, review, or improve REST APIs with Quarkus REST (Jakarta REST) — including resource classes, HTTP methods, status codes, request/response DTOs, Bean Validation, exception mappers, optional runtime OpenAPI exposure (SmallRye), contract-first generation from OpenAPI, content negotiation, pagination, sorting and filtering, API versioning, idempotency (Idempotency-Key), optimistic concurrency (ETag / If-Match), HTTP caching (Cache-Control), API deprecation (Sunset / Deprecation headers), RFC 7807 Problem Details, ISO-8601 for time in contracts, and security-aware boundaries. This should trigger for requests such as Review or improve JAX-RS resources in a Quarkus project; Design HTTP APIs with validation and error handling on Quarkus; Add API versioning, idempotency, ETag concurrency, or deprecation headers; Implement pagination, sorting, or RFC 7807 Problem Details error responses; Improve Quarkus REST resources and exception mappers. Part of Plinth Toolkit
日本語の概要は準備中です。原文の説明を表示しています。
jabrena/plinth☆ 4502026年10月13日 更新
Use when you need to apply functional exception handling best practices in Java — including replacing exception overuse with Optional and VAVR Either types, designing error type hierarchies using sealed classes and enums, implementing monadic error composition pipelines, establishing functional control flow patterns, and reserving exceptions only for truly exceptional system-level failures. This should trigger for requests such as Improve the code with Functional Exception Handling; Apply Functional Exception Handling; Refactor the code with Functional Exception Handling; Model Java errors with Result or Either types; Replace exception-heavy flows with functional error handling. Part of Plinth Toolkit
日本語の概要は準備中です。原文の説明を表示しています。
jabrena/plinth☆ 4502026年10月13日 更新
When the user needs to plan or execute a product launch — including pre-launch content sequences, launch funnels, JV/affiliate launches, cart open/close strategy, or evergreen launch funnels.
日本語の概要は準備中です。原文の説明を表示しています。
shawnpang/startup-founder-skills☆ 3532026年3月17日 更新
Guides implementation of the GDPR accountability principle under Articles 5(2) and 24, including documentation requirements for policies, DPIAs, RoPA, training records, and breach logs. Activate when establishing or reviewing accountability measures, preparing evidence portfolios, or demonstrating compliance to supervisory authorities. Keywords: accountability, Article 5(2), Article 24, documentation, compliance evidence, governance.
日本語の概要は準備中です。原文の説明を表示しています。
mukul975/Privacy-Data-Protection-Skills☆ 3072026年3月17日 更新
Guides a comprehensive organisational data protection audit against key GDPR requirements including Articles 5, 24, 25, 28, 30, 32, 35, and 37. Includes 50+ control points covering principles, accountability, security, and governance. Activate when performing compliance audits, preparing for supervisory authority inspections, or assessing organisational GDPR maturity. Keywords: data protection audit, compliance audit, GDPR audit, control points, accountability.
日本語の概要は準備中です。原文の説明を表示しています。
mukul975/Privacy-Data-Protection-Skills☆ 3072026年3月17日 更新
Think and work like an expert Antimicrobial Resistance Scientist. Use when a task calls for Antimicrobial Resistance Scientist judgment. Reasons from MIC distributions, ECOFFs, and phenotype–genotype concordance through EUCAST/CLSI AST, CARD/RGI and AMRFinderPlus resistomes, GLASS/WHONET/NARMS surveillance, carbapenemase/ESBL/MRSA mechanism panels, and heteroresistance PAP while treating breakpoint mixing, genotype-without-phenotype overclaim, selection-bias surveillance, and CARD version drift as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
K-Dense-AI/scientific-agents☆ 2082026年10月3日 更新
Peer benchmarking, multi-ticker financial comparison, growth value matrix, composite z-score ranking, industry peer comparison, competitive benchmarking, sector relative performance, peer group analysis, industry leader comparison, financial ratio benchmarking
日本語の概要は準備中です。原文の説明を表示しています。
agentii-ai/agentii-investment-intelligence☆ 2062026年9月29日 更新
Grounded in first principles, rigorously examine and refine a user's plan, task, decision, goal, strategy, proposal, or idea through structured, progressively deeper questioning, in order to bridge the gap between the User and the Agent. Use when the user explicitly requests grilling, challenge, pressure-testing, cross-examination, red-team review, pre-mortem analysis, or a decision audit. The goal is to uncover unclear objectives, hidden assumptions, contradictions, weak evidence, missing information, overlooked constraints, dependencies, risks, trade-offs, failure modes, and misalignment between intended outcomes and likely real-world results. Begin by establishing a shared understanding of the user's actual intent, goals, constraints, and success criteria. Ask focused, high-leverage questions rather than broad or repetitive ones. Adapt each question based on previous answers, probing deeper where uncertainty, unsupported assumptions, or strategic weaknesses remain. Regularly summarize the current understanding of the user's intent and position to confirm alignment, expose misunderstandings, and refine the problem or goal definition. Distinguish facts, assumptions, hypotheses, and unknowns. Challenge reasoning rigorously while remaining constructive, respectful, and solution-oriented. Continue until the reasoning is internally coherent, evidence-aware, constraint-conscious, risk-assessed, and translated into a clearer, more actionable goal, decision, or plan. Ultimately, achieving the super-alignment.
日本語の概要は準備中です。原文の説明を表示しています。
Inference1/clarify-intent-and-establish-shared-understanding☆ 2042026年10月10日 更新
Maps GWAS-implicated loci to candidate effector (causal) genes by integrating variant-to-gene (V2G) features via Open Targets L2G (Mountjoy 2021), MAGMA gene-based association (de Leeuw 2015), FUMA SNP2GENE, cS2G combined SNP-to-gene scores (Gazal 2022), Polygenic Priority Scores (PoPS, Weeks 2023), FLAMES, INQUISIT, DEPICT, and enhancer-gene predictors (ABC, ENCODE-rE2G). Use when narrowing a GWAS lead locus to a candidate causal gene, picking between proximity, eQTL-based, and similarity-based prioritizers, integrating multi-evidence streams (fine-mapping, colocalization, ABC enhancer-gene, distance, chromatin), reconciling discordant L2G vs PoPS calls, prioritizing tissue-specific eQTL evidence, or triangulating across at least three independent lines of evidence for a publication-grade effector-gene nomination.
日本語の概要は準備中です。原文の説明を表示しています。
BioTender-max/awesome-bio-agent-skills☆ 2012026年7月2日 更新
Performance optimization mindset - knowing when to optimize, how to measure, where bottlenecks hide, and when "fast enough" is the right answerUse when "slow, performance, optimize, profiling, benchmark, latency, throughput, cache, n+1, bottleneck, memory leak, too slow, speed up, response time, performance, optimization, profiling, caching, latency, throughput, big-o, benchmarking" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
omer-metin/skills-for-antigravity☆ 1652026年1月22日 更新
Performance optimization specialist for profiling, caching, and latency optimizationUse when "performance, latency, slow query, profiling, caching, optimization, N+1, connection pool, p99, performance, profiling, caching, latency, optimization, async, database, load-testing, ml-memory" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
omer-metin/skills-for-antigravity☆ 1652026年1月22日 更新
Git is deceptively simple to learn and incredibly hard to master. The difference between a team that ships and a team that fights merge conflicts all day comes down to workflow discipline. Your git history is documentation - make it tell a story future you can understand. This skill covers branching strategies (trunk-based, gitflow, GitHub flow), commit hygiene, merge vs rebase, conflict resolution, and the commands you actually need. Key insight: most git disasters come from not understanding what you're about to do. 2025 lesson: Trunk-based development with short-lived branches has won. Long-lived feature branches are a code smell. If a branch lives more than a few days, something is wrong with your architecture or process. Use when "git workflow, branching strategy, git merge, git rebase, merge conflict, git commit, trunk-based, gitflow, git history, git revert, git reset, git, version-control, workflow, branching, commits, merge, rebase, collaboration" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
omer-metin/skills-for-antigravity☆ 1652026年1月22日 更新
World-class accessibility design expertise combining the inclusive design principles of Microsoft's Inclusive Design team, the technical rigor of the W3C WCAG working group, and the lived experience perspective of disability advocates. Accessibility is not a feature - it's a fundamental quality attribute that makes products usable by everyone. Great accessibility design is invisible to those who don't need it and essential to those who do. It benefits everyone: captions help in noisy environments, keyboard navigation helps power users, high contrast helps in bright sunlight. When you design for the extremes, you improve the experience for all. Accessibility is not a checklist - it's a mindset that asks "who are we excluding?" at every design decision. Use when "accessibility, a11y, wcag, screen reader, keyboard navigation, color contrast, alt text, aria, focus management, skip link, assistive technology, inclusive design, ada compliance, section 508, accessible, voiceover, nvda, jaws, tab order, focus trap, accessibility, a11y, wcag, inclusive-design, screen-reader, keyboard-navigation, color-contrast, aria, focus-management, assistive-technology" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
omer-metin/skills-for-antigravity☆ 1652026年1月22日 更新