AutoGPT

Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause. Use when the user says "what changed in this contract over time", "show me the amendment history", "where's the latest [clause]", "how has [provision] evolved", or uploads multiple versions of an agreement.

The English summary is being prepared. Showing the original description.

Sort contract deviations by the user's playbook priority and route each one to its business owner or counsel.

The English summary is being prepared. Showing the original description.

Extract contract facts into a source-cited tracker without interpreting ambiguous language or giving legal advice.

The English summary is being prepared. Showing the original description.

Prepare a short source-backed brief that gives counsel the text, playbook gap, context, deadline, and exact decision needed.

The English summary is being prepared. Showing the original description.

Read an ad test by sample size and spread, and say whether there is a winner yet.

The English summary is being prepared. Showing the original description.

Find likely duplicate records with stated match rules and evidence, for a person to merge.

The English summary is being prepared. Showing the original description.

Audit CRM fields by fill rate, format, and use, and propose keep, fix, or retire for each.

The English summary is being prepared. Showing the original description.

Decide whether a CVE or advisory matters to the actual stack and show the data behind that judgement.

The English summary is being prepared. Showing the original description.

Use on the first conversation with Daniel, or whenever no finance preferences are saved yet: learn the revenue model, the books, the thresholds that count as too far, and where the numbers live, then get to a first read.

The English summary is being prepared. Showing the original description.

Prepare a data subject request reply with identity check, scope, deadline, and systems to search.

The English summary is being prepared. Showing the original description.

Create effective data visualizations with Python (matplotlib, seaborn, plotly). Use when building charts, choosing the right chart type for a dataset, creating publication-quality figures, or applying design principles like accessibility and color theory.

The English summary is being prepared. Showing the original description.

Set up a deal desk record from source evidence, approval rules, owners, dates, and a firm line between drafts and commitments.

The English summary is being prepared. Showing the original description.

Use for the money side of a deal: the deal P&L, margin floors and discount bands, approval routing, the concession log, and the mix impact of a price change.

The English summary is being prepared. Showing the original description.

Review a deal for evidence gaps across need, scope, stakeholders, process, competition, delivery, security, legal, and commercial approval.

The English summary is being prepared. Showing the original description.

Use when the user needs an ideal partner profile: who to recruit, in what tiers, what good looks like, and who to say no to.

The English summary is being prepared. Showing the original description.

Review a dependency change for breaking APIs, runtime shifts, supply-chain risk, test gaps, rollout risk, and rollback quality.

The English summary is being prepared. Showing the original description.

Build an evidence-backed inventory of direct, transitive, runtime, development, and container dependencies.

The English summary is being prepared. Showing the original description.

Plan a small, testable dependency upgrade with compatibility checks, owners, rollout evidence, and rollback steps.

The English summary is being prepared. Showing the original description.

Use when the user names developers, API adoption, docs, SDKs, or a bottom-up motion: the developer motion plan with funnel, content spine, and conversion points.

The English summary is being prepared. Showing the original description.

Set up dependency and security hygiene from repository evidence, with a clear scope, source list, risk queue, and approval line.

The English summary is being prepared. Showing the original description.

Draft a narrow dependency upgrade pull request with evidence, code changes, tests, risk notes, and rollback instructions.

The English summary is being prepared. Showing the original description.

Use when the portfolio needs program-level design: tiers, incentives, the MDF loop end to end, certifications, and enforced partner-system rules.

The English summary is being prepared. Showing the original description.

Build an auditable customer health score while keeping observed signals, judgement, and missing data separate.

The English summary is being prepared. Showing the original description.

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.

The English summary is being prepared. Showing the original description.