skills/message-outreach/SKILL.md
Convert raw person- or account-level data into a single, skimmable research brief for the sales team with Account, Persona, and ongoing research. Use when the user has prospect/account data and needs an actionable brief with ICP/ICA scoring.
npx skillsauth add alvarovillalbaa/agent-suite message-outreachInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Convert any pile of raw person‑ or account‑level data into a single, skimmable brief the sales team can act on immediately.
(Short background paragraph orienting a newcomer in <100 words.)
End with one forward‑looking question in italics.
Data ingestion: Accept JSON, CSV, or raw text. Normalize dates to ISO (YYYY‑MM‑DD) and currencies (e.g. €). Validate required fields: account name, contact name, contact role. If missing, annotate as N/A and log under “Follow‑Up Research.” Reject unsupported formats with a clear error message.
Evidence: Cite every fact inline (e.g. [LinkedIn:2025-07-20], [SalesNotes:RN-42]). For conflicting data, list variants with dates and choose the most recent with justification. Mark inferences (inferred) with brief logic.
Scoring (0–10): Geography, Tech Maturity, AI Adoption, Growth Stage, Decision Agility. Aggregate Fit = round(mean). Document bands (e.g. ARR, procurement cycle) per user context.
Output: Section order fixed; each section ≤200 words; bullets only; no extra sections.
Tone: Professional, concise, active voice. Metrics over adjectives. Every pain → specific next step; highlight one “killer insight” in bold.
development
Use for frontend engineering work such as components, routes, state management, accessibility, performance, design-system integration, and browser-facing debugging or refactors.
development
This skill should be used when the user asks to write, update, review, scaffold, move, remove, or continuously improve documentation for code, folders, services, repos, workflows, architectural decisions, or operational processes. Trigger for inline docs, `README.md`, `ARCHITECTURE.md`, `TESTS.md`, `SETUP.md`, `RUNBOOK.md`, `CHANGELOG.md`, `SECURITY.md`, `OVERVIEW.md`, `FAQ.md`, `DECISIONS.md`, `DEPENDENCIES.md`, `AGENTS.md`, `PLAN.md`, `SPEC.md`, `SOUL.md`, `PRINCIPLES.md`, `DESIGN.md`, `logs/`, `lessons/`, `items/`, `fixes/`, `audits/`, `raw/`, `plans/`, `specs/`, `sources/`, `lib/`, `references/`, `cookbook/`, `knowledge/`, `runbooks/`, `research/`, `official-documentation/`, `context/`, MDX docs, JSDoc/TSDoc, docstrings, ADRs, post-mortems, migration guides, documentation cleanups, and documentation-impact reviews.
tools
Cross-cloud CLI-first cloud operations for AWS, Azure, and GCP. Use when the assistant needs to identify which cloud provider or multi-cloud estate a repo uses, deploy new resources or services, wire automatic deployments, inventory and optimize infrastructure, or diagnose and repair cloud failures entirely from the terminal, with explicit approval gates for high-cost, destructive, identity-sensitive, or hard-to-reverse changes. Covers AWS Amplify full-stack projects, serverless workloads (Lambda, API Gateway, Step Functions, SAM, CDK), and the full AWS database portfolio (RDS, Aurora, Aurora DSQL, DynamoDB, ElastiCache), as well as deep Azure references for diagnostics, storage, compute, compliance, identity, Foundry, and cross-cloud migrations.
development
Use for backend engineering work such as APIs, services, data models, persistence, queues, caching, auth, background jobs, and server-side debugging or refactors.