AutoGPT

Package bookkeeping exceptions for the right owner with source facts, impact, urgency, and a precise decision request.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives. Covers structure, narrative framework, bad news delivery, and common mistakes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write ad variants that each test one idea, within platform limits and supported claims.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see emails. For sales collateral beyond emails, see sales-enablement.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build cohort and retention views with explicit entry events, return events, windows, eligibility, censoring, and sample sizes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Set up review and QA work from the repository, test setup, CI, release process, and merge rules.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Make a 15s vertical (9:16) code-built motion graphics advert for a user's business from THEIR website's real assets, built around one use case a chat LLM cannot do. Use for 'make an ad/promo/motion video for my product'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Performs security-focused differential review of code changes. Adapts analysis depth to codebase size, uses git blame for context, calculates blast radius by counting callers, checks test coverage of modified code, and generates a markdown report. Use when reviewing a PR, commit, or diff for security vulnerabilities, checking whether a change re-introduces a previously fixed bug, asking what else a change could break, or finding which modified code has no test covering it.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a deal involves a cloud consumption commit, a marketplace private offer, or a multi-year enterprise agreement.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use for month-end close support: the checklist with owners and status, accrual review, account reconciliations, control evidence, and audit preparation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write a client proposal, quote, scope of work, or engagement letter for a service business. Covers project understanding, scope, timeline, pricing presentation, and terms. Use whenever the user asks for a proposal, quote, project proposal, client proposal, SOW, statement of work, engagement letter, or B2B service engagement document — for web dev, consulting, trades, or any service business.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review churn risk from dated usage, outcome, support, relationship, and contract evidence, then propose the next check.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see emails. For in-app upgrade paywalls, see paywalls.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.