Import cookies from your real browser (Comet, Chrome, Arc, Brave, Edge) into the headless browse session for testing authenticated pages. Interactive picker UI or direct domain import. macOS Keychain integration.
日本語の概要は準備中です。原文の説明を表示しています。
4,372 件 ・ 関連度順
概要と使いどころ
Import cookies from your real browser (Comet, Chrome, Arc, Brave, Edge) into the headless browse session for testing authenticated pages. Interactive picker UI or direct domain import. macOS Keychain integration.
日本語の概要は準備中です。原文の説明を表示しています。
Restricts file edits to a specified directory. Pre-tool hooks intercept Edit and Write operations. Trailing-slash matching prevents partial path collisions.
日本語の概要は準備中です。原文の説明を表示しています。
Protein engineering and directed evolution analysis using Adaptyv Bio platform
日本語の概要は準備中です。原文の説明を表示しています。
Builds real-time communication systems with WebSockets or Socket.IO including bidirectional messaging, horizontal scaling with Redis, presence tracking, and room management.
日本語の概要は準備中です。原文の説明を表示しています。
Designs GraphQL schemas, implements Apollo Federation, builds real-time subscriptions, and optimizes queries with DataLoader and federation directives.
日本語の概要は準備中です。原文の説明を表示しています。
Remote command execution and file transfer on SageMaker HyperPod cluster nodes via AWS Systems Manager (SSM). This is the primary interface for accessing HyperPod nodes — direct SSH is not available. Use when any skill, workflow, or user request needs to execute commands on cluster nodes, upload files to nodes, read/download files from nodes, run diagnostics, install packages, or perform any operation requiring shell access to HyperPod instances. Other HyperPod skills depend on this skill for all node-level operations.
日本語の概要は準備中です。原文の説明を表示しています。
Initialize a PM Brain — a markdown-native second brain for a product operator (PM, product lead, founder, or anyone accountable for one product or initiative) doing judgment-heavy work with scattered inputs. Detects greenfield vs. migration mode, runs a focused interview, copies the deterministic scaffold into the working directory, populates placeholders from interview answers, runs a self-test, and commits. Use when invoked via `/pm-brain` or when the user asks to set up a PM Brain.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating Agent Skills packages (SKILL.md format) for Codex CLI, GitHub Copilot, or Amp - provides the agentskills.io specification with frontmatter constraints, directory structure, and validation rules
日本語の概要は準備中です。原文の説明を表示しています。
Your marketing director. Turns the buyer panel and the competitor map into positioning, the channels the target customer actually uses, a 30-day launch campaign with dated posts and ads, the first ten hooks, a budget split and the numbers to watch. Every message answers an objection real or simulated buyers raised. Use when the user says "how do I market this", "marketing plan", "launch campaign", "how do I get customers", "where do I advertise", "write my ads", or "positioning".
日本語の概要は準備中です。原文の説明を表示しています。
Your CFO. Builds the unit economics of a business before money is spent: what one unit earns after its direct costs, the real profit margin at the planned volume, the break-even point in units a day, year 1 month by month, the cash needed before it pays for itself, how long the startup spend takes to earn back, and what happens if the price drops, sales come in low or costs rise. Every number traces to an input the user can check. Use when the user says "find the profit margins", "do the numbers", "is this profitable", "break-even", "unit economics", "how much do I need to start", or "run the CFO".
日本語の概要は準備中です。原文の説明を表示しています。
Your brand designer. Names the business (with the trademark, domain and handle checks to run before falling in love with a name), writes the voice, a one-line promise and a tagline, and briefs the look: colours, type, logo and the first things a customer sees, so they match the positioning the marketing director chose. Use when the user says "name my business", "brand this", "logo", "brand identity", "what should it look like", "tagline", or "brand voice".
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Enforces staged execution discipline on large tasks: a written stage plan, parallel delegation where the runtime supports it, a failable verification check at each stage, and a skeptical self-review before delivery. Trigger when the user explicitly asks OR when the task objectively spans multiple files, sources, or sessions. Do NOT trigger on ordinary multi-step requests that a direct attempt handles fine (autonomous triggering only; explicit invocation always runs).
日本語の概要は準備中です。原文の説明を表示しています。
Run fable-mode execution discipline on Claude Haiku. Routes the task to the @fable-worker-haiku agent, whose definition carries the staged loop with tightened verification (no bare "unverified" allowed) and an escalate-don't-improvise rule. Trigger when the user explicitly asks for thorough/systematic handling run cheaply or fast ("fable on haiku", "deep work mode but cheap", "stage this on haiku"). For bulk mechanical work. Do NOT use for tasks needing synthesis — benchmark note: at n=1 the skill's effect on Haiku swung both directions (+25 / −17); route quality-critical work to fable-sonnet instead.
日本語の概要は準備中です。原文の説明を表示しています。
Generate scaffolds that gradually increase student choice, voice, and ownership within a learning task. Use when students depend heavily on teacher direction and need to develop autonomy.
日本語の概要は準備中です。原文の説明を表示しています。
Provide graduated assistance from abstract conceptual nudge to concrete procedural step, with reflection required before each escalation. Teaches help-seeking as a skill and prevents direct-answer shortcuts.
日本語の概要は準備中です。原文の説明を表示しています。
Design a structured goal-setting protocol using SMART or implementation-intention frameworks for students. Use when launching units, projects, or developing student self-direction habits.
日本語の概要は準備中です。原文の説明を表示しています。
Design a diagnostic hinge question that reveals whether students understand enough to move on. Use when planning key checkpoints mid-lesson during explicit or direct instruction.
日本語の概要は準備中です。原文の説明を表示しています。
Redesign a classroom as a prepared environment optimised for independent learning, calm transitions, and material access. Use when classroom layout hinders independence or self-directed work.
日本語の概要は準備中です。原文の説明を表示しています。
Design a checking-for-understanding protocol with specific techniques for each lesson stage. Use when planning systematic comprehension checks during explicit or direct instruction.
日本語の概要は準備中です。原文の説明を表示しています。
Redesign a direct instruction sequence to include productive struggle before the explanation phase. Use when teaching concepts that benefit from failure-first approaches.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," or "templated landing pages." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity/urgency, naming, and payment structure. Also use when the user mentions 'offer,' 'offer design,' 'build an offer,' 'grand slam offer,' 'irresistible offer,' 'value stack,' 'bonus stack,' 'guarantee,' 'risk reversal,' 'money-back guarantee,' 'scarcity,' 'urgency,' 'high-ticket offer,' 'productize a service,' 'naming an offer,' 'payment plan,' 'down-sell,' 'upsell offer,' or 'why isn't my offer converting.' Best for services, agencies, courses, coaching, info products, high-ticket B2B, and direct-response. If you run pure self-serve SaaS, read pricing first — tiers and packaging do more work there. For price level itself (tiers, freemium, value metric), see pricing. For the page that presents the offer, see copywriting. For the launch moment, see launch. For sales collateral, see sales-enablement.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use when the user mentions 'marketing council,' 'board of advisors,' 'advisory board,' 'what would Seth Godin say,' 'what would Ogilvy think,' 'channel Hormozi,' 'get multiple perspectives,' 'debate this,' 'have the council review,' 'marketing mentors,' or asks how a famous marketer would approach their problem. The council gives each advisor's take through their documented frameworks, surfaces where they disagree, and synthesizes a recommendation. For executing the winning direction, hand off to positioning, offers, copywriting, ads, or the relevant skill.
日本語の概要は準備中です。原文の説明を表示しています。