crm

Name: crm
Author: getnao

168stars52forks

How to install crm?

getnao/sylph/crm

$npx -y skills add getnao/sylph --skill crm

Installs into the current project.

Summary

Reference skill for working with the Twenty CRM. Detailed setup and schema docs live in admin/crm/README.md.

Files · 1

View on GitHub

SKILL.md

1	# CRM
2
3	Reference skill for working with the Twenty CRM. Detailed setup and schema docs live in `admin/crm/README.md`.
4
5	## MCP connectors
6
7	\| Connector \| Purpose \|
8	\|-----------\|---------\|
9	\| CRM \| Read and update contacts, deals, activities \|
10
11	## Quick reference
12
13	- CRM: Twenty (self-hosted)
14	- MCP tools: Use the Twenty MCP server - always start with `get_tool_catalog`
15	- Detailed docs: `admin/crm/README.md`
16
17	## Key patterns
18
19	1. Always discover tools first - call `get_tool_catalog` before any CRM operation
20	2. Learn before executing - call `learn_tools` to get input schemas for unfamiliar tools
21	3. Group-by for analytics - use group_by tools for comparative/aggregate queries
22	4. Find for records - use find tools for retrieving specific records
23	5. Multiple metrics - run multiple group_by calls and merge results
24
25	## Common operations
26
27	\| Task \| Approach \|
28	\|------\|----------\|
29	\| Look up a company \| `find` by company name \|
30	\| Check deal pipeline \| `group_by` stage, sum ARR \|
31	\| Get contact details \| `find` by company or email domain \|
32	\| Update a deal stage \| `execute_tool` with the update tool \|
33
34	## Guardrails
35
36	- Never delete CRM records - archive or flag instead
37	- Never bulk-update without confirmation - show the change list first
38	- Always verify ambiguous matches - if a search returns multiple results, ask
39	- Log significant changes - note CRM updates in the relevant agent's log
40
41	## Self-improvement
42
43	After the CAO corrects a CRM operation or query:
44
45	1. If the correction reveals a CRM schema quirk (e.g. "use display name not slug for deal stages"), add it to the Key patterns section above
46	2. If a common operation is missing from the Quick reference table, add it
47	3. Update `admin/crm/_insights.md` with the correction and the right approach
48	4. If a new tool or query pattern proves reliable, add it to the Common operations table

People who liked this also viewed

6 picks

Type

crm

168stars52forks

View on GitHub

How to install crm?

getnao/sylph/crm

$npx -y skills add getnao/sylph --skill crm

Installs into the current project.

Summary

Reference skill for working with the Twenty CRM. Detailed setup and schema docs live in admin/crm/README.md.

Files · 1

View on GitHub

SKILL.md

1	# CRM
2
3	Reference skill for working with the Twenty CRM. Detailed setup and schema docs live in `admin/crm/README.md`.
4
5	## MCP connectors
6
7	\| Connector \| Purpose \|
8	\|-----------\|---------\|
9	\| CRM \| Read and update contacts, deals, activities \|
10
11	## Quick reference
12
13	- CRM: Twenty (self-hosted)
14	- MCP tools: Use the Twenty MCP server - always start with `get_tool_catalog`
15	- Detailed docs: `admin/crm/README.md`
16
17	## Key patterns
18
19	1. Always discover tools first - call `get_tool_catalog` before any CRM operation
20	2. Learn before executing - call `learn_tools` to get input schemas for unfamiliar tools
21	3. Group-by for analytics - use group_by tools for comparative/aggregate queries
22	4. Find for records - use find tools for retrieving specific records
23	5. Multiple metrics - run multiple group_by calls and merge results
24
25	## Common operations
26
27	\| Task \| Approach \|
28	\|------\|----------\|
29	\| Look up a company \| `find` by company name \|
30	\| Check deal pipeline \| `group_by` stage, sum ARR \|
31	\| Get contact details \| `find` by company or email domain \|
32	\| Update a deal stage \| `execute_tool` with the update tool \|
33
34	## Guardrails
35
36	- Never delete CRM records - archive or flag instead
37	- Never bulk-update without confirmation - show the change list first
38	- Always verify ambiguous matches - if a search returns multiple results, ask
39	- Log significant changes - note CRM updates in the relevant agent's log
40
41	## Self-improvement
42
43	After the CAO corrects a CRM operation or query:
44
45	1. If the correction reveals a CRM schema quirk (e.g. "use display name not slug for deal stages"), add it to the Key patterns section above
46	2. If a common operation is missing from the Quick reference table, add it
47	3. Update `admin/crm/_insights.md` with the correction and the right approach
48	4. If a new tool or query pattern proves reliable, add it to the Common operations table

People who liked this also viewed

6 picks

Type