529 件 ・ 関連度順
概要と使いどころ
AI Agent Workflow & Skill Architecture Guide — turn expert work into measurable, reusable agent systems. Covers workflow discovery, skill decomposition, harness design, evaluation, human escalation, observability, cost control, and multi-agent orchestration. Includes a measured marketing-delivery case: 15 people × 3–4 weeks reduced to one strategist + AI in 5 days. By Gingiris.
日本語の概要は準備中です。原文の説明を表示しています。
Build or audit a financial model — 3-statement model (P&L, cash flow, balance sheet), scenario analysis, and sensitivity tables. Use when asked to "build a financial model", "model our growth scenarios", or "what happens to runway if we hire 5 people".
日本語の概要は準備中です。原文の説明を表示しています。
Build onboarding playbook - day 1 through week 4 checklist, access provisioning, context transfer, and success milestones. Use when asked to "build an onboarding process", "how do we onboard new hires", or "reduce time to productivity for new joiners".
日本語の概要は準備中です。原文の説明を表示しています。
Design performance management system - review cycles, calibration process, career ladder, and PIP framework. Use when asked to "build a performance review process", "design career levels", "how do we handle underperformers", or "run a review cycle".
日本語の概要は準備中です。原文の説明を表示しています。
Build a hiring pipeline - job description, sourcing strategy, interview scorecard, and offer process. Use when asked to "write a job description", "build an interview process", "design our hiring funnel", or "what should we look for in a [role]".
日本語の概要は準備中です。原文の説明を表示しています。
Document and strengthen company culture - values articulation, team norms, communication protocols, and culture health diagnostics. Use when asked to "define our values", "document how we work", "diagnose culture health", or "write team norms".
日本語の概要は準備中です。原文の説明を表示しています。
Design compensation framework - salary bands, equity philosophy, offer templates, and total comp benchmarking. Use when asked to "design our comp bands", "how much equity should we give", "is our comp competitive", or "write an offer template".
日本語の概要は準備中です。原文の説明を表示しています。
Run human-to-agent migration - audit which roles can be agent-assisted or replaced, design the transition playbook, and manage the offboarding of displaced roles. Use when asked to "which roles can agents replace", "how do we transition to AI-first ops", or "build our agent migration plan".
日本語の概要は準備中です。原文の説明を表示しています。
Design or review org structure - spans of control, reporting lines, role clarity, headcount plan, and team topology. Use when asked to "design our org", "should we restructure", "what is the right team structure", or "plan headcount for next year".
日本語の概要は準備中です。原文の説明を表示しています。
The Relic of a father-and-son relationship — not a person, but the pattern between two people: long silences, shared repairs, and a truce that never needed saying out loud. 父子关系的 Relic：蒸馏的不是某个人，而是两个人之间的模式——沉默、一起修东西、无需说出口的和解。
日本語の概要は準備中です。原文の説明を表示しています。
The Relic of a retiring engineering lead — judgment, intuition, and the way he taught people, kept after the person left the building. 一位退休技术主管的「专家 Relic」：人离开了公司，判断逻辑、经验直觉和带人的方式留下来。
日本語の概要は準備中です。原文の説明を表示しています。
Methods for assessing what people actually eat — 24-hour recall, food frequency questionnaires, diet diaries, biomarkers, duplicate-plate studies, and controlled feeding. Covers the relative strengths and biases of each instrument, how to choose among them for a given question, and how to interpret results in the presence of measurement error. Use when a user wants to estimate population-level intake, individual-level intake, or evaluate the plausibility of a dietary claim that depends on how intake was measured.
日本語の概要は準備中です。原文の説明を表示しています。
Household-scale nutrition planning that treats meals as a weekly system, not a series of independent decisions. Covers macronutrient balance, the plate method, weekly rotation, leftover architecture, pantry-to-plate translation, and the food-safety floor that every meal plan must meet. Use when building a weekly menu, adapting a diet to a new household member, planning for a week of predictable meals on a budget, or teaching a learner how a kitchen feeds people over time.
日本語の概要は準備中です。原文の説明を表示しています。
Study of human activities, spatial patterns, and social processes on Earth's surface. Covers population and migration, cultural diffusion and landscapes, urbanization and city systems, economic geography and development, political geography and borders, and social/identity geographies. Use when reasoning about why people live where they do, how cultures spread, how cities grow, how economies are spatially organized, or how power operates through space.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze the causal system-wide impact of a proposed change across behavior, interfaces, state/data, runtime dependencies, tests, documentation, controls, people/processes, and model/prompt/context behavior. Use before planning when lexical reference search is insufficient to establish blast radius and verification obligations.
日本語の概要は準備中です。原文の説明を表示しています。
Use for Deepline GTM work that searches, enriches, scores, collects signals, or automates a workflow: find companies or people, enrich a CSV, find emails or LinkedIn, compare providers, build a waterfall, create a webhook or cron, or write a Play. For live information work, run a small heterogeneous experiment, exploit the observed winner, and reopen misses. Skip pure copywriting and non-GTM research.
日本語の概要は準備中です。原文の説明を表示しています。
GTM prospecting, enrichment, outreach, and Deepline Play work/audits. Providers: adyntel,affinity,ai_ark,akta,allegrow,amplemarket,apify,attention,attio,aviato,bettercontact,bigquery,bluesky,bounceban,brave,browserbase,builtwith,cbinsights,clay,clickhouse,cloudflare,contactout,contextdev,crunchbase,crustdata-v3,customer_db,databricks,dataforseo,datagma,dealroom,deepline_ip_to_company,deepline_native,deeplineagent,discolike,dropleads,edges,emailbison,emailguard,enformion,enigma,exa,findymail,firecrawl,fireflies,firmable,forager,fullenrich,fundable,generic_http,getleads,gong,google_ads_audiences,google_workspace,govfiles,grain,hackernews,harvestapi,heyreach,hubspot,hunter,icypeas,instantly,intercom,ipqs,kaspr,kernel,leadmagic,lemlist,limadata,linkedin_ads_audiences,luma,lusha,meta_audiences,millionverifier,nooks,notion,openmart,opensosdata,openwebninja,outreach,parallel,peopledatalabs,pitchbook,podscan,polymarket,postgres,predictleads,prospeo,quickenrich,rapidapi,redshift,rocketreach,salesforce,salesforge,….
日本語の概要は準備中です。原文の説明を表示しています。
Use when finding real role-holders at known company domains from an ICP, especially prompts like 'find all job titles at these companies', 'find qualified titles', 'find RevOps or marketing-ops buyers', or when exact title discovery should precede paid people search.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' or 'consumer behavior.' This skill provides 70+ mental models organized for marketing application.
日本語の概要は準備中です。原文の説明を表示しています。
Neural search via Exa MCP for web, code, and company research. Use when the user needs web search, code examples, company intel, people lookup, or AI-powered deep research with Exa's neural search engine.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a set of candidate Skills or app capabilities is technically valid but still needs to become a clear, useful ChatGPT/Codex Plugin that people can understand, discover, and invoke for real work.
日本語の概要は準備中です。原文の説明を表示しています。
Use whenever the user wants to find, shortlist, vet, or enrich US public-relations and communications agencies — media relations, crisis comms, investor relations (IR), product-launch PR, tech/startup PR, healthcare PR, B2B PR, public affairs, brand reputation, and internal communications. Triggers on "find me a tech PR agency in NY", "shortlist three IR firms for our IPO", "we need crisis comms help for a brand reputation issue", or "pull contact info for these 10 PR firm domains", even when described indirectly (we need press, get us into TechCrunch, manage our brand reputation). Drives the ServiceGraph API (api.servicegraph.co) — a 100k+ US firm catalog filterable by industry, services, location, size, ratings. Defer to find-marketing-agency when scope is broader marketing beyond PR/comms. Skip in-house PR/comms hires, "write me a press release" DIY asks, PR-software comparisons (Cision, Muck Rack), influencer-marketplace questions, non-US firms, individual freelance PR people.
日本語の概要は準備中です。原文の説明を表示しています。
Use whenever the user wants to find, rank, or shortlist directories and listing sites where they can submit an AI product — an AI tool, AI app, AI agent, or agent skill / plugin — to get backlinks, referral traffic, and discovery. Triggers on "where can I list my AI tool", "directories to submit my AI agent", "agent-skills directories", "best AI tool directories for backlinks", "where do I get my GPT/Claude app discovered", or "pull submission details for these AI-directory domains", even when described indirectly (we built an AI agent, where do we get it in front of people). Drives the ServiceGraph API (api.servicegraph.co) — a catalog of 1,000+ product directories enriched with Domain Rating, backlinks, and organic traffic. Defer to find-mcp-directories for MCP-server listings specifically, and to find-product-directories for general SaaS/software/app launches with no AI angle. Skip finding an AI consultancy/agency to hire (use find-ai-consultancy), comparing AI products ("ChatGPT vs Claude"), building an AI tool (do-the-work), and AI link-building *services*.
日本語の概要は準備中です。原文の説明を表示しています。
Write the postmortem for an incident, in its incident channel, once it is mitigated or resolved. Use on "write up this incident", "postmortem", "incident summary", "what happened here for people who weren't around", "draft the retro", or when the oncall memory says incidents of this severity get one. Reads the incident channel (and the alert thread it came from), the investigation findings and the data behind them, and writes a one-screen, zero-context write-up: what happened, impact with numbers, detection, timeline with durations, why it happened, what fixed it, follow-ups with proposed owners, and one before/during/after chart. Posted and pinned in the incident channel as its final pinned post, with edit requests updating that one pinned post in place — unless the person or the team's conventions say write-ups live elsewhere, in which case it is written there and only a link is posted, nothing pinned. A person edits and publishes it; never assigns blame.
日本語の概要は準備中です。原文の説明を表示しています。