AutoGPT

Use before a reply, script, macro, or KB article goes out in a regulated segment: check it against the regimes in play and route what fails.

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

Take a competitor apart in a way that changes a decision: what they promise, who they are built for, where they are weak, and what we should do about it.

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

When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.

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

Use when the user names a competitor, a battlecard, or win-loss, or asks how you win against someone: the CI brief with landscape, change blocks, pricing read, and win strategy.

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

Find and explain company policies in plain language. Trigger with "what's our PTO policy", "can I work remotely from another country", "how do expenses work", or any plain-language question about benefits, travel, leave, or handbook rules.

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

Set up communications work from facts, spokespeople, approved messages, approval owners, and off-limits topics.

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.

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.

Profile and explore a dataset to understand its shape, quality, and patterns. Use when encountering a new table or file, checking null rates and column distributions, spotting data quality issues like duplicates or suspicious values, or deciding which dimensions and metrics to analyze.

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.

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.

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.

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.

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.

Use when the user names a release, a launch date, or a launch tier, or asks whether the business is ready to launch: the readiness assessment, sequenced plan, enablement spec, and 90-day measure.

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

Use when an outsourced support vendor handles your customers: audit the queue, score the sample, calibrate the vendor, and lift capability with evidence.

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

Set up a safe bookkeeping intake: reporting period, source records, chart of accounts, owners, approval rules, and open gaps.

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