attio-crm

casper-studios/casper-marketplace · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/casper-studios/casper-marketplace --skill attio-crm
0 commentsdiscussion
summary

Interact with Attio CRM to manage companies, contacts, notes, and deals programmatically.

skill.md

Attio CRM

Overview

Interact with Attio CRM to manage companies, contacts, notes, and deals programmatically.

Quick Decision Tree

What do you need?
├── Get/search companies
│   └── references/api-guide.md
│   └── Script: scripts/attio_api.py get-company / search-companies
├── Create/update company
│   └── Script: scripts/attio_api.py create-company / update-company
├── Create/link contacts
│   └── Script: scripts/attio_api.py create-person
├── Add notes to records
│   └── Script: scripts/attio_api.py create-note
└── Parse Attio URLs
    └── Script: scripts/attio_api.py parse-url

Environment Setup

# Required in .env
ATTIO_API_KEY=your_api_key_here

Get your API key: Attio Settings → Developers → API Keys

Required Scopes

Scope Operations
record:read Get/search companies and people
record:write Create/update companies and people
note:read List and get notes
note:write Create and delete notes

Common Usage

Search Companies

python scripts/attio_api.py search-companies "Acme Corp" --limit 10

Get Company

python scripts/attio_api.py get-company <record_id>

Create Company

python scripts/attio_api.py create-company "Microsoft" --domain "microsoft.com"

Create Contact

python scripts/attio_api.py create-person "[email protected]" --first-name "John" --last-name "Smith"

Add Note

python scripts/attio_api.py create-note <record_id> "Meeting Notes" "Discussion summary..."

Rate Limits

  • 100 requests per minute
  • Automatic retry with exponential backoff

Cost

Free - Attio API has generous free tier.

Security Notes

Credential Handling

  • Store ATTIO_API_KEY in .env file (never commit to git)
  • Generate keys in Attio: Settings > Developers > API Keys
  • Rotate keys periodically or if compromised
  • Never log or print API keys in script output

Data Privacy

  • CRM contains sensitive customer and prospect information
  • Company records include business details and contact info
  • People records contain PII (names, emails, phone numbers)
  • Notes may contain confidential meeting discussions
  • Avoid exporting full CRM data unnecessarily

Access Scopes

  • Request minimum required scopes:
    • record:read - Read companies and people (read-only)
    • record:write - Create/update records (write access)
    • note:read - Read notes (read-only)
    • note:write - Create notes (write access)
  • API keys can be scoped to specific permissions

Compliance Considerations

  • PII Protection: Customer data is subject to privacy regulations
  • GDPR: EU customer data requires GDPR compliance
  • Data Minimization: Only access/export data you need
  • Audit Trail: Log CRM operations for compliance auditing
  • Data Retention: Follow organizational data retention policies
  • Access Control: Limit API key distribution to authorized users
  • Customer Consent: Ensure proper consent for data processing

Troubleshooting

Common Issues

Issue: Invalid field ID / slug

Symptoms: "Field not found" or "Invalid attribute" error Cause: Field slug doesn't match Attio workspace configuration Solution:

  • Check field slugs in Attio: Settings > Objects > Fields
  • Field slugs are case-sensitive (e.g., company_name not Company_Name)
  • Custom fields have unique slugs - verify exact spelling
  • Use API to list available fields if unsure

Issue: Rate limited

Symptoms: 429 status code or "rate limit exceeded" Cause: Exceeding 100 requests per minute limit Solution:

  • Implement exponential backoff between requests
  • Batch multiple operations into single requests where possible
  • Add delays (600ms+) between consecutive requests
  • Queue requests and process gradually

Issue: Record not found

Symptoms: "Record not found" error with known record Cause: Invalid record ID, deleted record, or wrong object type Solution:

  • Verify record ID from Attio URL or previous API response
  • Check if record was deleted or merged
  • Ensure using correct object type (companies vs people)
  • Use search endpoint to find record by name/email

Issue: API key invalid

Symptoms: 401 Unauthorized or "invalid API key" Cause: Key expired, revoked, or incorrectly configured Solution:

  • Regenerate API key in Attio: Settings > Developers > API Keys
  • Verify ATTIO_API_KEY is correctly set in .env
  • Check for leading/trailing whitespace in key
  • Ensure key has required scopes for operation

Issue: Insufficient permissions

Symptoms: "Forbidden" error or missing data Cause: API key missing required scopes Solution:

  • Review key scopes in Attio: Settings > Developers > API Keys
  • Create new key with required scopes (record:read, record:write, etc.)
  • For notes: ensure note:read and note:write scopes
  • Workspace admin may need to grant additional permissions

Issue: Duplicate record created

Symptoms: Same company/person appears multiple times Cause: No deduplication on create, or different field values Solution:

  • Search before creating to check for existing records
  • Use primary identifier (domain for companies, email for people)
  • Consider using update-or-create pattern
  • Merge duplicates manually in Attio UI

Resources

  • references/api-guide.md - Complete API documentation
  • references/integration.md - CRM integration patterns

Integration Patterns

Meeting Notes to CRM

Skills: transcript-search → attio-crm Use case: Add meeting summaries to company records Flow:

  1. Search transcript-search for client meetings
  2. Extract key points, action items, and summary
  3. Create note on Attio company record with meeting details

Research to CRM

Skills: parallel-research → attio-crm Use case: Enrich CRM records with research data Flow:

  1. Run parallel-research on company for latest info
  2. Extract funding, team size, tech stack, news
  3. Update Attio company record with enriched fields

Voice Agent to CRM

Skills: voice-agents → attio-crm Use case: Log AI call summaries to CRM Flow:

  1. Voice agent completes discovery or feedback call
  2. Extract call summary and key insights
  3. Add note to Attio record with call summary and next steps
how to use attio-crm

How to use attio-crm on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add attio-crm
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/casper-studios/casper-marketplace --skill attio-crm

The skills CLI fetches attio-crm from GitHub repository casper-studios/casper-marketplace and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/attio-crm

Reload or restart Cursor to activate attio-crm. Access the skill through slash commands (e.g., /attio-crm) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.569 reviews
  • Liam Srinivasan· Dec 20, 2024

    attio-crm has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Xiao Shah· Dec 20, 2024

    I recommend attio-crm for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Amina Iyer· Dec 16, 2024

    attio-crm is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Pratham Ware· Dec 12, 2024

    Useful defaults in attio-crm — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Diya Diallo· Dec 12, 2024

    attio-crm fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Michael White· Dec 12, 2024

    Useful defaults in attio-crm — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Michael Johnson· Dec 8, 2024

    Solid pick for teams standardizing on skills: attio-crm is focused, and the summary matches what you get after install.

  • Min Malhotra· Dec 4, 2024

    attio-crm reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Min Chawla· Nov 27, 2024

    We added attio-crm from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Liam Iyer· Nov 11, 2024

    attio-crm fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 69

1 / 7