「each」の検索結果

Complete beginner-friendly cold email toolkit. Walks from zero to launched campaign — domain purchase, inbox setup, list building, copywriting, enrichment, and sending via Smartlead or Instantly. Use when setting up cold email for the first time, launching a new campaign, teaching someone cold email, or when you need an end-to-end guide that bundles strategy, copy, infrastructure, and API references in one place.

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

Pulls replies from a Smartlead campaign, classifies each as positive/neutral/negative/OOO/bounce/unsubscribe using Claude, and reports the positive reply rate — the north-star metric for cold email. Use when the user wants to know if a campaign is actually working (not just getting replies, but getting the RIGHT replies). Triggers on "score my replies", "how's campaign X doing", "positive reply rate", "is this campaign working".

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

User-facing entry point for the wp-rocket issue workflow. Invoke directly to start a delivery run from a GitHub issue number, URL, or raw description. Runs inline in your conversation context; spawns specialist agents (ticket-writer, grooming-agent, challenger, backend-agent, frontend-agent, release-agent, lead-reviewer, qa-engineer) as isolated sub-agents; invokes supporting skills (knowledge-graph, dod, docs, issue-workflow) inline. Routes based on structured JSON outputs from each agent, manages loop counters, handles escalations, and maintains a live HTML run log.

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

Read one conversation window and return every independently mutable claim it states, one record each, with who or what it is about, whether it happened or stands, and the words that carry its time. Used by the memory extraction model on every conversation window; the engine resolves dates, validates keys, and repairs format.

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

Define how multiple brands, sub-brands, and product lines relate to each other under one organization. Use when the user says "brand architecture", "sub-brand", "brand portfolio", "master brand", "house of brands", "branded house", "product naming system", "how do our brands relate", "parent brand", "brand hierarchy", "brand family", "we have multiple products and need a naming system", "brand extension", "new product launch under existing brand", or when a company has grown beyond a single brand and needs a system to manage brand relationships.

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

Build brand partnership strategy — co-branding campaigns, brand collaborations, licensing deals, partner brand alignment, and joint marketing. Use when the user says "brand partnership", "brand collab", "co-branding", "brand collaboration", "partnership marketing", "brand alliance", "co-branded product", "licensing deal", "partner with another brand", "brand collaboration strategy", "how do we partner with brands", "co-marketing partnership", "joint campaign", or wants to build credibility, reach, or revenue through alignment with another brand.

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

Build a brand's messaging hierarchy — taglines, value propositions, key messages, and proof points for each audience. Use when the user says "brand messaging", "messaging framework", "value proposition", "tagline", "brand tagline", "key messages", "messaging hierarchy", "what should we say about our brand", "brand copy foundation", "messaging architecture", "elevator pitch", "one-liner", "brand statement", or needs consistent language across all communications. Also use when messaging feels inconsistent across channels or teams.

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

Find and remove unreachable/unused code safely. Use during cleanup or before a refactor.

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

Startup diagnostic router. Use FIRST when a founder doesn't know where to start, has multiple overlapping problems, or asks a vague question like 'what's wrong with my startup', 'why aren't people buying', 'what should I focus on', 'where do I even begin', 'nothing is working'. Routes to the right framework from the 15 available skills — or tells you when no framework fits and you just need to go talk to people. This is the entry point. Use it before reaching for any specific skill.

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

Execute implementation plan by dispatching fresh subagent for each task, with code review between tasks

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

Find affiliate programs in the OpenAffiliate registry, then confirm every term on the brand's own page and report each one with a verbatim quote and its source URL. Use this skill when the user wants affiliate terms they can rely on: before signing up, before publishing a review or comparison, when a listing looks outdated, or when two sources disagree. Also trigger for: "verify this affiliate program", "is X's affiliate commission still 30%", "what's the cookie length for X", "check the affiliate terms", "does X have an affiliate program", "find a recurring program and confirm the terms", "is this commission rate real", "source for X's affiliate terms", "fact-check this affiliate program", "what does X pay affiliates".

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

Take 1 blog post or article and generate 15-30 platform-native micro-content pieces. Not reformatting — re-contextualizing for each platform's culture. Triggers on: "atomize this content", "repurpose my blog post", "turn this into social posts", "content atomizer", "pillar content", "one to many content", "repurpose content", "multiply my content", "content explosion", "turn article into posts", "break down this article", "micro content from blog", "content pillar strategy", "10x my content", "platform-native content", "atomize", "content multiplication".

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

Rank and summarize the user's own WeChat Moments (朋友圈) feed so real life events and genuine information rise above promotion and small talk, weighted by how much the user actually talks to each author. Use when the user says 'summarize my Moments', 'read my 朋友圈', 'what did I miss on Moments', 'rank my Moments', or 'check my WeChat Moments'.

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

Market and engage on Reddit authentically. Use when the user says "Reddit marketing", "Reddit strategy", "promote on Reddit", "Reddit post", "subreddit strategy", "Reddit outreach", "Reddit ads", or asks about marketing or building presence on Reddit.

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

Plan, produce, and market a podcast. Use when the user says "podcast strategy", "start a podcast", "podcast marketing", "podcast growth", "podcast SEO", "show notes", "podcast monetization", "guest outreach", or asks about launching, growing, or promoting a podcast.

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

Research and enrich B2B leads using the Apollo.io API. Use when the user says "find leads", "prospect research", "company enrichment", "find decision makers", "B2B leads", "lead research", "enrich contacts", "find VP of marketing at", or asks about finding people at specific companies or in specific roles.

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

Audit and reorganize a Claude Code / Codex skill library — enforce a naming convention (prefix each skill by which backend or product it touches), rename skills consistently, fix the symlinks and cross-references a rename breaks, and report broken symlinks and stale name references. Use when the user says "organize my skills", "rename these skills", "clean up the skill library", "enforce a skill naming convention", or "fix broken skill symlinks".

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

Make a 10–30 second continuous-shot explainer for any product, rendered from code to MP4 with sound. One hero element (a ball, a cursor, a file, a message) travels through the product's workflow laid out as stations on one big canvas; the camera follows it, each station reacts as it passes, then the camera pulls out to reveal the whole journey. Use when someone wants an engaging, story-driven, one-take explainer or a loopable product animation.

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

MCP threat-model artifact for a scaffolded harness. Reports allowed/denied tools, dangerous permissions count, secrets reachability, network/shell/file-write grants, default-deny posture. Verdict: clean (exit 0) / medium (exit 1) / high (exit 2). The 'enterprise gold' artifact for PR + compliance review.

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

List the available harness templates and what each one ships with. Use when the user asks "what templates are available", "what verticals does the harness generator support", or "show me what I can scaffold".

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

Loyalty program airline ticketing partnerships (alliance + bilateral). Cross-references credit card currencies to booking programs for award reachability checks.

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

Automate the full QuarkPanTool → mswnlz GitHub content publishing pipeline. Supports Quark / Baidu / Aliyun drives with multi-account rotation. Use when the user provides share URLs and wants: (1) auto-detect drive type and route to correct handler, (2) save resources with automatic account rotation, (3) clean junk files from shared folders, (4) copy promotional files into each folder, (5) generate permanent encrypted share links, (6) auto-classify items into local content dirs (book/movies/AIknowledge/tools/etc.), (7) append/update YYYYMM.md and README index, (8) local git commit, (9) send unified Telegram notifications to multiple groups, (10) rebuild site and deploy to Cloudflare Pages.

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

Step 5 of the PaperOrchestra pipeline (arXiv:2604.05018). Iteratively refine drafts/paper.tex by simulating peer review and applying targeted revisions, with strict accept/revert halt rules, deterministic 0-100 decision bands (Accept/Minor/Major/Reject) that drive a target-met early stop, and a Devil's Advocate concession-threshold guard that blocks acceptance on unresolved critical findings. Maintains a worklog and snapshots each iteration so revert is real, not symbolic. TRIGGER when the orchestrator delegates Step 5 or when the user asks to "refine the draft", "iterate on the paper", or "run peer review on this paper".

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

Make 100 versions of Claude fight to the death over one task. Spins up N sub-agents (default 100, --quick for 16), gives every one the exact same task plus a different strategy card (reasoning mode, workflow, strategy), then runs a single-elimination bracket: they attack each other's solutions, defend and revise, and a judge scores every match on a written rubric until one solution survives. Use when the user is not satisfied with an answer, calls it a bad answer, says try again or do better, says "arena", or asks to make them compete.

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