Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

crm-adapter-attio

Étoiles1

Forks0

Mis à jour28 avril 2026 à 15:34

Two-way sync between markdown CRM and Attio. Same shape as crm-adapter-airtable but mapped to Attio's object model (Companies, People, Deals, Notes). Markdown stays canonical; Attio is a working surface. Conflicts surfaced, never auto-merged.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

danielrosehill

danielrosehill/Claude-Career-Plugin

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	crm-adapter-attio
description	Two-way sync between markdown CRM and Attio. Same shape as crm-adapter-airtable but mapped to Attio's object model (Companies, People, Deals, Notes). Markdown stays canonical; Attio is a working surface. Conflicts surfaced, never auto-merged.
disable-model-invocation	false
allowed-tools	Read, Write, Bash(test ), Bash(date )

CRM Adapter — Attio

Same contract as crm-adapter-airtable, but for Attio. Use this when the user is already living in Attio for personal CRM (common for indie consultants).

Markdown remains the source of truth.

Inputs

$ARGUMENTS:

Required: --direction=<push|pull|two-way>.
Optional: --object=<companies|people|deals|all> — default all.
Optional: --dry-run.

Prerequisites

Attio MCP or API token configured.
Config:
- CRM_ADAPTER=attio
- ATTIO_WORKSPACE_ID
- ATTIO_OBJECT_COMPANIES, ATTIO_OBJECT_PEOPLE, ATTIO_OBJECT_DEALS — Attio object slugs (default companies, people, deals).

Schema mapping

crm/companies.md ↔ Attio Companies:

markdown column	attio attribute
slug	`domains.domain` (or custom `Slug` text attr)
name	`name`
domain	`domains`
status	`categories` (or custom select)
size	custom `Size`
hq	`primary_location`
notes	linked `Notes`
last-touch	custom `Last Touch` (date)

crm/outreach.md ↔ a custom Outreach object (created on first run if missing) or treated as Attio Notes against the linked Company. Default: custom Outreach object.

crm/opportunities.md ↔ Attio Deals.

People (recipients) are upserted into Attio People with the company link; markdown rows reference recipient name + email only.

Procedure

Identical to crm-adapter-airtable (load both sides → diff → apply per direction → surface conflicts → manifest at .attio-sync.json), differing only in:

API calls go through Attio MCP/REST.
slug is keyed via the company's primary domain by default; configurable via ATTIO_SLUG_ATTR.
Outreach object: if ATTIO_OBJECT_OUTREACH not present, propose creating a custom object on first run (asks the user).

Conflict handling

Same as airtable adapter — write to crm/.conflicts-<date>.md, never auto-resolve.

Print summary

direction: <push|pull|two-way>
pushed: <n>  pulled: <n>  unchanged: <n>  conflicts: <n>
manifest: .attio-sync.json
custom-objects-created: <list, if any>

Guardrails

Markdown canonical.
Don't create a custom Attio object without asking — Attio object schema is sticky.
If a user has a non-default object schema, the user's mapping in config wins.

Failure modes

Missing Attio credentials → bail with setup steps.
Required custom attribute missing → ask the user whether to create it (one prompt per attribute).
API rate limit → checkpoint and exit cleanly.

Plus depuis ce dépôt

même dépôt

bulk-verify-crm

danielrosehill/Claude-Career-Plugin

Sweep all (or a filtered subset of) email addresses in the workspace CRM and re-verify them via Hunter Email-Verifier. Use periodically — people change jobs, addresses go stale, accept-all status changes. Updates the `verified` and `last-verified` columns in `crm/contacts.md` and prints a summary of what flipped.

2026-04-301

detect-mcps

danielrosehill/Claude-Career-Plugin

Scan the user's existing Claude Code plugins and MCP servers to detect capabilities the career plugin needs (email send, transcription, calendar/tasks, semantic store, CRM). For each capability, decide whether to reuse an already-installed plugin/MCP, install a recommended companion plugin, or add an MCP server. Writes the resolution map to ${CAREER_DATA_DIR}/config.json under a `capabilities` block. Invoked from /career:onboard before install-companion-plugins so we don't double up on capabilities the user already has.

2026-04-301

enrich-contact

danielrosehill/Claude-Career-Plugin

Enrich an existing CRM contact with Hunter Combined-Enrichment — pulls role, seniority, department, social handles, and the contact's company facts in one call. Use to flesh out a thinly-populated CRM row before drafting outreach or prepping for a meeting. Operates on an email address from the CRM; updates the row in place.

2026-04-301

find-email-by-name

danielrosehill/Claude-Career-Plugin

Given a person's name and their company (name or domain), return Hunter's best guess at their email address with a confidence score. Use when the user already knows who they want to reach and just needs the address. Differs from find-contact (which lists candidates at a company) — this is targeted at a single named person.

2026-04-301

verify-email

danielrosehill/Claude-Career-Plugin

Validate a single email address via Hunter Email-Verifier. Use when the user has an address (handed to them, scraped, guessed) and wants a deliverability + confidence read before sending outreach. Returns Hunter's verdict (deliverable / risky / undeliverable / unknown), score, and the disposable / role / accept-all flags. Does not write to the CRM unless asked.

2026-04-301

vector-conflict-check

danielrosehill/Claude-Career-Plugin

For CONTEXT_STORE=pinecone — verify the index against the local workspace. Flags vectors whose source file was deleted, renamed, or content-changed (hash mismatch), and surfaces vectors whose content contradicts current ground-truth (stale claims, closed engagements, outdated targets). Proposes deletes/re-embeds; never silently mutates the index.

2026-04-281

name	crm-adapter-attio
description	Two-way sync between markdown CRM and Attio. Same shape as crm-adapter-airtable but mapped to Attio's object model (Companies, People, Deals, Notes). Markdown stays canonical; Attio is a working surface. Conflicts surfaced, never auto-merged.
disable-model-invocation	false
allowed-tools	Read, Write, Bash(test ), Bash(date )

CRM Adapter — Attio

Same contract as crm-adapter-airtable, but for Attio. Use this when the user is already living in Attio for personal CRM (common for indie consultants).

Markdown remains the source of truth.

Inputs

$ARGUMENTS:

Required: --direction=<push|pull|two-way>.
Optional: --object=<companies|people|deals|all> — default all.
Optional: --dry-run.

Prerequisites

Attio MCP or API token configured.
Config:
- CRM_ADAPTER=attio
- ATTIO_WORKSPACE_ID
- ATTIO_OBJECT_COMPANIES, ATTIO_OBJECT_PEOPLE, ATTIO_OBJECT_DEALS — Attio object slugs (default companies, people, deals).

Schema mapping

crm/companies.md ↔ Attio Companies:

markdown column	attio attribute
slug	`domains.domain` (or custom `Slug` text attr)
name	`name`
domain	`domains`
status	`categories` (or custom select)
size	custom `Size`
hq	`primary_location`
notes	linked `Notes`
last-touch	custom `Last Touch` (date)

crm/outreach.md ↔ a custom Outreach object (created on first run if missing) or treated as Attio Notes against the linked Company. Default: custom Outreach object.

crm/opportunities.md ↔ Attio Deals.

People (recipients) are upserted into Attio People with the company link; markdown rows reference recipient name + email only.

Procedure

Identical to crm-adapter-airtable (load both sides → diff → apply per direction → surface conflicts → manifest at .attio-sync.json), differing only in:

API calls go through Attio MCP/REST.
slug is keyed via the company's primary domain by default; configurable via ATTIO_SLUG_ATTR.
Outreach object: if ATTIO_OBJECT_OUTREACH not present, propose creating a custom object on first run (asks the user).

Conflict handling

Same as airtable adapter — write to crm/.conflicts-<date>.md, never auto-resolve.

Print summary

direction: <push|pull|two-way>
pushed: <n>  pulled: <n>  unchanged: <n>  conflicts: <n>
manifest: .attio-sync.json
custom-objects-created: <list, if any>

Guardrails

Markdown canonical.
Don't create a custom Attio object without asking — Attio object schema is sticky.
If a user has a non-default object schema, the user's mapping in config wins.

Failure modes

Missing Attio credentials → bail with setup steps.
Required custom attribute missing → ask the user whether to create it (one prompt per attribute).
API rate limit → checkpoint and exit cleanly.