「eth」の検索結果

Core agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.

日本語の概要は準備中です。原文の説明を表示しています。

Maintain injected credential authenticators, method-isolated caching, request-context propagation, and the pure-Go SQLite API-key plugin. Excludes interactive portal password authentication and identity-store provisioning.

日本語の概要は準備中です。原文の説明を表示しています。

Iteratively edit and refine a named plan for a task through a conversational loop. Each round, the current plan is shown and the user is asked whether to keep refining, mark the plan as done, or proceed to the implementation or draft. Use when the user wants to plan a task purely through chat-driven refinement.

日本語の概要は準備中です。原文の説明を表示しています。

Skill Optimization: Auto Research. Autonomously optimize any Claude Code skill by running it repeatedly, scoring outputs against binary evals, mutating the prompt, and keeping improvements. Based on Karpathy's autoresearch methodology. Use when: optimize this skill, improve this skill, run autoresearch on, make this skill better, self-improve skill, benchmark skill, eval my skill, run evals on. Outputs: an improved SKILL.md, a results log, and a changelog of every mutation tried.

日本語の概要は準備中です。原文の説明を表示しています。

Creates B2B sales narrative decks using April Dunford's methodology. Outputs slide-by-slide Markdown outline plus optional PPTX generation. For external sales prospects.

日本語の概要は準備中です。原文の説明を表示しています。

Use when you want a B2B sales deck based on April Dunford's methodology, with a slide-by-slide narrative and optional PPTX output.

日本語の概要は準備中です。原文の説明を表示しています。

Interactive workshop that builds a monthly rolling editorial calendar using MKT1 methodology. Walks through Perceptions, content pillars, themes, and capacity to produce a 4-week detailed plan plus 3-month roadmap. Designed to be re-run monthly.

日本語の概要は準備中です。原文の説明を表示しています。

Create irresistible offers and pitches using Alex Hormozi's methodology from $100M Offers. Guides through value equation, guarantee frameworks, pricing psychology, and creating offers "too good not to take" for any product or service.

日本語の概要は準備中です。原文の説明を表示しています。

Inspect and manually purge the Soniox artifacts — transcriptions and uploaded audio files — that offline transcription leaves behind, on dev or prod. Use when offline transcription silently stops working, when Soniox answers 429 `limit_exceeded`, when `SonioxTranscriberTest.OfflineTranscribeWorks` and `CleanerDeletesEnqueuedArtifacts` fail together, or when the user says "sweep Soniox", "soniox/sonoix sweep", "sonoix swipe", "purge Soniox", "check Soniox files", or "is Soniox at the cap".

日本語の概要は準備中です。原文の説明を表示しています。

CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Three modes: SCOPE EXPANSION (dream big), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials).

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks about evolution progress, current scores, best version, how many iterations ran, or whether the loop is stagnating.

日本語の概要は準備中です。原文の説明を表示しています。

LLM brand manipulation — build a consensus web so ChatGPT, Claude, Perplexity, and Google AI Overviews mention your brand when people ask about your category. Uses surround sound methodology, entity SEO, and LLM citation science. Use when "get mentioned in AI", "LLM brand presence", "surround sound", "AI search visibility", "Perplexity ranking", "ChatGPT mentions", "AI Overview inclusion", "entity authority", "brand mentions in AI", or any request to influence how AI systems perceive and recommend your brand.

日本語の概要は準備中です。原文の説明を表示しています。

Pull performance data for published content across every surface — LinkedIn, Dev.to, Google Search Console, GA4, and AI citation tracking (Perplexity, Anthropic, OpenAI). Grades each piece as winner, average, or underperformer and surfaces whether an AI search engine has cited it.

日本語の概要は準備中です。原文の説明を表示しています。

Ship a complete go-to-market deliverable pack for a client as a cross-linked set of private HTML pages topped by a client hub (the ask, tool install, access grants, ordered signup checklist). Use when "GTM plan for [client]", "put together a GTM", "go to market plan", "build the client hub", "attach everything for the client", "package this for the client", or when an engagement's plan/audit/emails must be delivered as linked pages rather than loose files.

日本語の概要は準備中です。原文の説明を表示しています。

Use when 高教社杯/CUMCM mathematical modeling papers need lightweight literature search, citation verification, method/background references, standards or policy sources, Chinese-English source routing, DOI/BibTeX checks, or claim-to-citation mapping without fabricated sources.

日本語の概要は準備中です。原文の説明を表示しています。

Use for .NET test design and validation with xUnit v3, Moq, focused regression tests, command tests, service/manager tests, code generation tests, Roslyn helper tests, MiniDb isolation, HTTP stubs, temp directories, and deciding whether to run targeted tests or builds.

日本語の概要は準備中です。原文の説明を表示しています。

Use for Perigon documentation work across this workspace, especially Perigon.docs/Content/docs/Perigon bilingual and versioned docs, syncing zh-CN and en-US content, updating docs from Perigon.CLI, Perigon.template, and Perigon.Modules changes, and deciding whether to revise existing pages or add new documentation.

日本語の概要は準備中です。原文の説明を表示しています。

Go-to-market engineering for the Yupcha portfolio (OmniVoice-Studio, the Clay-alternative in this repo, ResuBird). A closed set of executable verbs — research, audit, draft, measure, prepare, publish, escalate — each with a typed contract, required sources, and a risk tier. Use when: (1) researching ICP/competitors/channels/prior art, (2) auditing our own properties for what's actually broken (dead pricing pages, 404ing clone URLs, unfilled demos, licence detection, watermark coverage), (3) drafting docs/comparison pages/release notes/launch copy, (4) measuring real numbers against GOAL.md, (5) preparing a Show HN or a listing up to the send button, (6) any question about whether a GTM action is allowed. Triggers: 'gtm', 'go to market', 'launch', 'show hn', 'growth', 'marketing', 'positioning', 'icp', 'competitors', 'outreach', 'cold email', 'audit our', 'is it ok to', 'can we post', 'promote'.

日本語の概要は準備中です。原文の説明を表示しています。

Odoo 20 development knowledge base covering actions, controllers, data files, API decorators, SQL constraints, indexes, modules, fields, manifests, mixins, ORM methods, migrations, OWL components, performance, QWeb reports, security, testing, transactions, translations, and XML views. Use when writing, reviewing, or debugging Odoo 20 Python, XML, or JavaScript code, creating or modifying modules, fixing performance issues, or looking up Odoo 20 API patterns and best practices.

日本語の概要は準備中です。原文の説明を表示しています。

Odoo 19 development knowledge base covering actions, controllers, data files, API decorators, SQL constraints, indexes, modules, fields, manifests, mixins, ORM methods, migrations, OWL components, performance, QWeb reports, security, testing, transactions, translations, and XML views. Use when writing, reviewing, or debugging Odoo 19 Python, XML, or JavaScript code, creating or modifying modules, fixing performance issues, or looking up Odoo 19 API patterns and best practices.

日本語の概要は準備中です。原文の説明を表示しています。

Trace Odoo execution flow from an entry point through controllers, button actions, cron jobs, model methods, overrides, computes, onchanges, constraints, database operations, security checks, and side effects. Use before implementation, during debugging, impact analysis, performance review, or code review when behavior depends on Odoo call chains.

日本語の概要は準備中です。原文の説明を表示しています。

用户在投资或重大决策中面临诱惑性选择时激活：想做空被高估的股票、想加杠杆抄底、想投资"研究过但不确定是否真懂"的标的、频繁交易、试图通过看K线择时。 不适用于：纯信息查询（"某公司PE多少"）、已确定不碰的日常小事、需要正面分析方法的场景（如"怎么分析护城河"）。 关键触发信号："我觉得可以试试做空""这次例外应该没问题""我已经研究了一段时间应该算懂了""短期做个波段"。 本skill通过排除法（Stop Doing List）帮助用户识别并停止做错的事情，核心原则：发现错了立刻停止，不管多大代价都是最小代价。

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill whenever the user wants to analyze binaries with radare2/r2 from the command line, including reverse engineering, disassembly, function analysis, strings/import inspection, patching, binary diffing, hex inspection, or r2 scripting. Also use it when the user mentions PE/ELF/Mach-O/DEX/WASM files together with CLI analysis, `rabin2`, `rasm2`, `radiff2`, `r2pipe`, or asks for radare2 command help on Windows/Linux/macOS.

日本語の概要は準備中です。原文の説明を表示しています。

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for IPA runtime analysis, Frida hooks, Objective-C or Swift method tracing, Keychain inspection, SSL pinning bypass, URL scheme handling, and iOS request-signing recovery. Use when the user asks to hook an IPA, trace Objective-C or Swift runtime behavior, inspect Keychain or plist state, bypass pinning, analyze deeplinks or universal links, or replay accepted iOS requests. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

日本語の概要は準備中です。原文の説明を表示しています。