2,307 件 ・ 関連度順
概要と使いどころ
DCF valuation model for A-share stocks using Chinese financial data. Uses AkShare MCP for financial statements, WACC inputs (risk-free rate from China government bond yields), and growth projections. Use instead of the original dcf-model skill for Chinese equities.
日本語の概要は準備中です。原文の説明を表示しています。
Generates a streak tracking system with timezone-aware day boundaries, streak freeze protection, and streak-at-risk push notifications. Use when user wants daily/weekly engagement streaks, consecutive day tracking, or habit tracking.
日本語の概要は準備中です。原文の説明を表示しています。
Crypto market scanner and single-token analyst - movers scans top winners/losers/trending or on-chain runners with pump-risk flags; single-token produces a verdict-first deep report for one token.
日本語の概要は準備中です。原文の説明を表示しています。
Review open PRs two ways - default is a per-PR deep review with severity-tagged findings, inline comments, and a verdict; --survey runs a risk-tiered triage digest of what's safe to merge first
日本語の概要は準備中です。原文の説明を表示しています。
Adversarially review a grooming spec before implementation starts. Finds hidden risks, unvalidated assumptions, and missing dependencies. Standalone entry point for the challenger agent.
日本語の概要は準備中です。原文の説明を表示しています。
Compare two schema states and surface the risky changes. Use before applying migrations or after a model change.
日本語の概要は準備中です。原文の説明を表示しています。
Local user-profile maintenance skill for Codex, Claude Code, OpenClaw, OpenCode, and other agent harnesses. Use only when the user explicitly invokes $user-profile-keeper to create, initialize, update, query, correct, delete, export, or audit a local persistent user profile. It can extract durable collaboration preferences, requirement-expression habits, capability boundaries, recurring omissions, risk preferences, privacy boundaries, and typical events from the current session into auditable, confirmable, retractable local profile data. Do not auto-invoke, upload profile data, or replace task-clarifier's normal clarification flow.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user already has a FINISHED video and wants Higgsfield to repurpose, restyle, clip or analyze it: Shorts Studio (restyle one 4–120s source video into a set of short-form clips from a style preset), Clipify (turn one YouTube video into subtitled clips), Virality Predictor (predict virality, hook strength, attention, retention risk with a dashboard), or Video Analysis (scene-by-scene breakdown of an uploaded video or a YouTube link). Also use when the user asks which of these cost credits and which are free, 'turn my video into shorts', 'will this go viral', 'score my ad', 'break this video down scene by scene'. Names: shorts_studio_create, shorts_studio_create_preset, shorts_studio_list_presets, shorts_studio_status, clipify, virality_predictor, brain_activity, video_analysis_create, video_analysis_status.
日本語の概要は準備中です。原文の説明を表示しています。
Your operations manager. Works out how the business actually runs on day one: suppliers and what they cost, who works when, the step-by-step routines for opening, serving or shipping and closing, the tools to run it, the licences and permits to check, and a risk register with what to do when each thing goes wrong. Feeds real costs back to the CFO. Use when the user says "how do I run this", "operations", "suppliers", "staffing", "SOPs", "what do I need to open", "permits", or "day one".
日本語の概要は準備中です。原文の説明を表示しています。
Your board of directors. Puts a business idea in front of a three-member board, each a sub-agent reading the idea through one published framework: the Offers lens (from Alex Hormozi's $100M Offers), the Monopoly lens (from Peter Thiel's Zero to One) and the Product lens (from Walter Isaacson's biography of Steve Jobs). Each member scores the idea, names the risks that would kill it and votes fund, fund with conditions, or pass. Use when the user says "test my business idea", "would this work", "pressure-test this", "what would a board say", "is this a good business", or starts the founder pack on a new idea.
日本語の概要は準備中です。原文の説明を表示しています。
7-section readiness scorecard for a LOCAL repo. Reports repo type + agent topology + MCP risk + test confidence + release readiness + recommended harness plan + scorecard. Exit 0 ready, 1 needs-work, 2 blocked. --json for the 6-field scorecard, --bundle for the ADR-031 schema-1 envelope.
日本語の概要は準備中です。原文の説明を表示しています。
5-dimension scorecard (0-100, grade A/B/C/F) for a scaffolded harness. Dimensions: Repo understanding (25%), Agent usefulness (25%), MCP safety (20%), Test coverage (15%), Publish readiness (15%). Emits a 6-field badges block (score + mcpRisk + 4 booleans) ready for the harness README. Exit 0 A/B, 1 C, 2 F.
日本語の概要は準備中です。原文の説明を表示しています。
Use for authorized security assessment of LLM applications and AI agents, including prompt injection, tool abuse, RAG exposure, memory poisoning, and model supply-chain risks.
日本語の概要は準備中です。原文の説明を表示しています。
Reverse JavaScript-based custom DSL/VM interpreters, non-standard WASM-like runtimes, and risk-control engines. Use when analyzing IIFE or switch-based opcode dispatchers, extracting instruction tables, recovering bytecode semantics, capturing VM state at runtime, or reconstructing execution flow.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to see what the agent assumes about a phase's approach, order, scope, risks and dependencies before planning starts, instead of running a full discuss session. Read-only; ends with a prompt for feedback.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific decisions. Use this skill when users ask to pitch a new research idea, work through a project problem, evaluate project risks, plan research strategy, navigate decision trees, or get help choosing what scientific problem to work on. Typical requests include "I have an idea for a project", "I'm stuck on my research", "help me evaluate this project", "what should I work on", or "I need strategic advice about my research".
日本語の概要は準備中です。原文の説明を表示しています。
Rollback procedures, risk assessment, pre/post-deployment validation, and contingency planning. Load when orchestrating deployment or preparing rollback plans. For deployment strategy details (canary, blue-green, rolling), see `cicd-and-deployment` skill.
日本語の概要は準備中です。原文の説明を表示しています。
Dung khi goi ban chua du hap dan va can dong goi lai — value stack, bonus, bao hanh va dao nguoc rui ro, ly do gap rut co that, cau truc upsell va downsell, dong goi dich vu thanh san pham ban duoc. Kich hoat khi user nhac 'thiet ke offer', 'offer khong convert', 'value stack', 'bonus stack', 'guarantee', 'risk reversal', 'upsell downsell', 'goi coaching', 'khach thay dat qua', 'ban gi thi khach moi mua'. Khong dung cho — chon con so gia va bac goi thi dung skill 17-pricing-strategy; offer MIEN PHI de doi thong tin lien he thi dung skill 70-lead-magnet; viet copy ban offer da chot thi dung skill 05-copy-quang-cao.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a WINNING ad has to be scaled without breaking it — readiness checks, vertical scaling at plus 20 to 30 percent per step, horizontal scaling into new audiences, creatives, and channels, learning-phase reset risk, how Advantage+ and Performance Max behave when scaled, creative refresh cadence, and the signals that mean stop. Trigger on 'scale ads', 'increase the ad budget', 'scale a winner', 'CPA went up after I scaled', 'how fast can I scale', 'it worked at 50 a day and broke at 200'. Not for — fixing an account that is not working yet, see `03-performance-eval-global`; warm audience plans, see `56-retargeting-plan-global`; proving the winner first, see `19-ab-test-setup-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user needs an overall marketing plan for a period — objectives, segments, positioning, channel mix, content direction, budget, timeline, KPIs, and a risk matrix, adapted to US, EU, SEA, or LATAM. Trigger on 'marketing plan', 'marketing strategy for next year', 'go-to-market roadmap', 'plan for Q3', 'we have no marketing plan', 'where should we spend next quarter'. Also use when a founder only says the business needs to grow and has no idea which channel to start with. Not for — one specific campaign, see `02-campaign-brief-global`; working backward from a revenue goal to spend, see `10-reverse-kpi-global`; splitting a budget across channels and months, see `61-budget-planning-global`; taking a brand new product to market, see `59-go-to-market-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a specific campaign needs a brief the whole team can execute from — context, objective, audience, core message, creative direction, channels, deliverables, week-by-week timeline, approval gates, and risks. Trigger on 'campaign brief', 'creative brief', 'launch brief', 'brief the team on this campaign', 'we are running a promo next month', 'what is the plan for this campaign'. Also use when the user describes a promotion out loud and asks for something the team can actually run. Not for — the whole period plan, see `00-marketing-plan-global`; the list of design files needed, see `41-campaign-asset-list-global`; assigning work to one person, see `64-team-brief-global`; a new product launch sequence, see `59-go-to-market-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the WHAT being sold needs work, not the price and not the copy — core promise, value stack, bonuses, guarantee and risk reversal, honest scarcity and urgency, tier packaging, upsell and downsell paths, and high-ticket or productized service structures. Trigger on 'design an offer', 'irresistible offer', 'value stack', 'add a guarantee', 'my offer is not converting', 'people say it is too expensive'. Also use when traffic and copy are fine and nobody is buying anyway. Not for — the number on the price tag, see `17-pricing-strategy-global`; the ad text selling it, see `05-ad-copy-global`; the page it sits on, see `12-landing-page-brief-global`; the launch sequence, see `59-go-to-market-global`.
日本語の概要は準備中です。原文の説明を表示しています。
Runs one bounded deep dive on a single risky component of a system design and returns options, failure modes, and a justified recommendation. Use during a design session when a component needs expert depth beyond the main thread's budget.
日本語の概要は準備中です。原文の説明を表示しています。
Finds Zephyr Scale test cases linked or relevant to Jira stories, ACs, modules, and release risks. Use for coverage analysis and traceability checks.
日本語の概要は準備中です。原文の説明を表示しています。