Add a Field
Skill8 starsChanged 5 months agoMITView on GitHub
Add or change a custom field on the CRM records, and surface it where it's needed. Creates a text / number / date / dropdown field (e.g. broker name, settlement date, bank) in CRM settings, then optionally puts it on the opportunity card display and includes it in the relevant workspace spreadsheet — so the operator self-serves a field change end to end instead of filing a request and waiting.
In this repository101 other files it gives its agents.
- templates/CLAUDE.mdCLAUDE.md
- Assemble Content PackSkill
- Assemble PackSkill
- Audit My AutomationsSkill
- Audit My DataSkill
- automate-thisSkill
- Brand My WorkspaceSkill
- Break Down A ChannelSkill
- Build Brand StrategySkill
- Build Customer VoiceSkill
- Build DocumentSkill
- Build FormSkill
- Build Knowledge Base From DocsSkill
- Build My ProofSkill
- Build My VoiceSkill
- Build Social StrategySkill
- Build SpreadsheetSkill
- Build Work Order ProcessSkill
- Cash Flow ForecastSkill
- Coach My CallsSkill
- Compare DocumentsSkill
- Connect A ToolSkill
- Delegate This WorkSkill
- Describe A ProductSkill
- Design My ScenesSkill
- Design Nurture SequenceSkill
- draft-replySkill
- Email Me A ReportSkill
- Estimate My BASSkill
- Extract DocumentSkill
- Find My Next MoveSkill
- Five Day ChallengeSkill
- Follow-up RadarSkill
- Form RadarSkill
- Get Found OnlineSkill
- Grill Me On This DecisionSkill
- import-from-anywhereSkill
- lead-triageSkill
- Learn My BusinessSkill
- Lint DocumentSkill
- Lint FormSkill
- Lint Nurture SequenceSkill
- log-this-callSkill
- make-it-happenSkill
- Make My VideoSkill
- Make Product DemoSkill
- Make Social PostSkill
- Make ThumbnailSkill
- missed-call-recoverySkill
- Nurture HealthSkill
- Onboard Team MemberSkill
- Outstanding DocumentsSkill
- Outstanding InvoicesSkill
- Package My VideoSkill
- Plan My AdsSkill
- Plan My ContentSkill
- Plan My RoadmapSkill
- Plan My YouTubeSkill
- Prep For CallSkill
- Price My WorkSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
Add the custom field to that record's settings (CRM settings → additional fields, via the platform's settings/custom-field tools).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Add a Field
Custom fields are how the CRM fits a specific business. This adds one and wires it to where it's actually used, in one pass.
Step 1 — Confirm the field
Get, in one short batch:
- Name (e.g. "Broker name", "Settlement date").
- Type — text, number, date, or dropdown. If dropdown, the options (e.g. the broker names). If a value set is small and stable, prefer a dropdown over free text so the data stays clean and filterable.
- Which record — opportunity, contact, or company.
Step 2 — Create it in CRM settings
Add the custom field to that record's settings (CRM settings → additional
fields, via the platform's settings/custom-field tools). Use the exact name and
type confirmed. If a write returns 202 (queued for approval), surface it and stop
(knowledge/safeguards.md).
Step 3 — Offer to surface it where it's used
A field nobody can see isn't much use. Offer (and do, on a yes):
- On the opportunity card — add it to the card display so it shows at a
glance on the pipeline (
/settings/crmcard display). - In a spreadsheet — if there's a workspace spreadsheet this field belongs in
(e.g. settlement date → the monthly settlement sheet), add it as a column
(hand off to
/build-spreadsheet).
Tell the operator these two options explicitly; don't assume. A new field often needs both to be useful.
Step 4 — Confirm
✓ Added "Broker name" (dropdown: Dom, Sam, Priya) to opportunities.
• Shown on the opportunity card ✓
• Added to the "Monthly settlement" spreadsheet ✓
Set it on a record and it'll flow through to both.Hard rules
- ❌ Don't guess the type or options — confirm them (a stable small set = dropdown, not text).
- ❌ Don't route around an approval gate.
- ✅ Always offer the card-display + spreadsheet surfacing; a hidden field is half-done.
- ✅ Use the exact field name everywhere so it matches across CRM, card, and spreadsheet.
Output shape
A one-line confirmation naming the field + type (+ options), and which surfaces it was added to (card / spreadsheet), or the offer to add it to those if the operator hasn't said yet.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

