Skip to content

getnao/sylph / .claude/skills/sylph-setup-skill

sylph-setup-skill

Verified

Set up a specific Sylph skill by auto-pulling examples from the web, deriving insights, and configuring the skill. Run as `/sylph-setup-skill <skill-name>`.

FileKindSize
SKILL.mdskill md6.4 KB
setup-blog.mdmarkdown4.3 KB
setup-brand.mdmarkdown4.5 KB
setup-contracts.mdmarkdown5.8 KB
setup-create-issue.mdmarkdown4.9 KB
setup-crm.mdmarkdown2.5 KB
setup-customer-report.mdmarkdown5.9 KB
setup-customer-success.mdmarkdown5.8 KB
setup-email.mdmarkdown3.5 KB
setup-events.mdmarkdown3.8 KB
setup-hr.mdmarkdown4.2 KB
setup-investor-update.mdmarkdown3.1 KB
setup-linkedin.mdmarkdown5.1 KB
setup-newsletter.mdmarkdown4.9 KB
setup-outbound.mdmarkdown5.1 KB
setup-reddit.mdmarkdown4.1 KB
setup-slack-community.mdmarkdown6.0 KB
setup-substack.mdmarkdown4.0 KB
setup-website.mdmarkdown3.6 KB
setup-x.mdmarkdown3.6 KB
setup-zero-inbox.mdmarkdown6.6 KB

setup-crm.md

View on GitHub
# Setup: CRM

Guide for setting up the CRM skill with the CAO's pipeline, fields, and workflow.

## Prerequisites

- Global setup complete (`/sylph-setup`)
- CRM access (HubSpot, Salesforce, Pipedrive, or similar)

## Step 1: Identify the CRM

CRM configuration is internal and can't be derived from the web. Ask the CAO two questions:

1. **"What CRM do you use?"** (HubSpot, Salesforce, Pipedrive, Close, Attio, Twenty, or other)
2. **"What are your pipeline stages?"** (e.g., Lead -> Qualified -> Demo -> Proposal -> Closed Won/Lost. For each stage: what does it mean, and what triggers a move to the next?)

That's it. Everything else gets derived from her answers and the CRM connection.

## Step 2: Check for MCP connection

1. Check `.mcp.json` for an existing CRM MCP server.
2. If connected, use the MCP to pull:
   - Pipeline stages and their definitions
   - Key deal fields
   - Key contact fields
   - Recent activity types
3. If not connected, work from the CAO's answers and note that manual setup is needed.

## Step 3: Write insights

From the CAO's answers and any MCP data, write to `sales/crm/_insights.md`:

```markdown
# CRM Insights

## Platform
- CRM: [platform name]
- MCP connection: [connected / not connected / manual]

## Pipeline stages
| Stage | Definition | Exit criteria |
|-------|-----------|---------------|
| [stage] | [what it means] | [what moves deal forward] |

## Key fields
- Deal: [important deal fields]
- Contact: [important contact fields]
- Company: [important company fields]

## Activity logging
- [what gets logged and how]

## Reports
- [regular reports and their purpose]

## Hygiene rules
- [stale deal alerts, required fields, etc.]
```

Save CRM reference to `sales/crm/_examples/pipeline-overview.md`:

```yaml
---
date: YYYY-MM-DD
type: crm-reference
crm: [platform]
notes: "Pipeline and field reference"
---
```

## Step 4: Confirm with the CAO

Present the pipeline summary:

> "Here's what I have: [CRM platform], [number] pipeline stages from [first] to [last]. Key deal fields are [fields]. Does this look right? Any hygiene rules or regular reports I should know about?"

Incorporate her corrections.

## Step 5: Configure the skill

Open `.claude/skills/sales/crm/SKILL.md` and fill in:

- CRM platform and connection method
- Pipeline stage definitions
- Field mapping (what to read, what to update)
- Activity logging rules
- Report templates

## Step 6: Test

Run a CRM query (e.g., "show me deals closing this month") to verify the connection works. Capture any configuration notes in `sales/crm/_insights.md`.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall