Sets price, structures packages and tiers, and designs the monetization surfaces that carry them — upgrade paths, paywalls, and offer construction. Use this to set or change pricing, design or restructure tiers, choose a pricing metric, build an offer, design upgrade prompts and paywalls, or evaluate whether a pricing change is safe to make.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
The highest-leverage number in the business and the least examined. Most companies are underpriced and have never tested it.
Choose what you charge per before choosing how much. It should scale with the value the customer receives, be predictable enough to budget, and be something they cannot easily game.
Get this wrong and no amount of tuning the number fixes it — a metric that scales with your cost rather than their value creates a permanent argument at every renewal.
Anchor on value delivered, not cost incurred. Cost sets a floor and nothing else.
Evidence to gather: what the alternative costs them today including labor, what similar categories charge, and what current customers say about price — with the caveat that nobody says a price is too low. Willingness-to-pay research is directional, not decisive; people misreport.
If nobody ever objects to your price, it is too low. Some loss on price is correct.
Tiers should map to distinguishable segments with different needs, not to arbitrary feature counts. Three is usually right; more creates paralysis and support load.
Each tier needs one obvious reason to upgrade, tied to something that grows with the customer's success. Gating on a feature they will never need does not drive upgrades; gating on a limit they will hit does.
Name tiers for who they are for, not by metal. "Team" and "Business" tell a buyer where they belong.
Upgrade prompts and paywalls should appear at the moment of blocked value — when someone is trying to do the thing the tier does not allow, not on a schedule.
Explain what is behind the gate and why the limit exists. An unexplained wall reads as extraction. Show the value already received before asking for payment, and make declining easy — dark patterns buy one conversion and lose the account.
references/sources.md in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.
日本語の概要は準備中です。原文の説明を表示しています。
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.
日本語の概要は準備中です。原文の説明を表示しています。
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.
日本語の概要は準備中です。原文の説明を表示しています。
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.
日本語の概要は準備中です。原文の説明を表示しています。
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.
日本語の概要は準備中です。原文の説明を表示しています。