communication-history
Skill28 starsChanged 43 days agoApache-2.0View on GitHub
Retrieve activity history (calls, emails, notes, meetings, tasks) for a CRM record and assemble pre-call briefs.
In this repository18 other files it gives its agents.
- audience-targetingSkill
- bulk-operationsSkill
- conversation-history-briefSkill
- conversation-inbox-triageSkill
- crm-data-qualitySkill
- crm-lookupSkill
- customer-retentionSkill
- custom-object-managementSkill
- data-enrichmentSkill
- deal-managementSkill
- quote-to-cashSkill
- sales-executionSkill
- sales-reportingSkill
- team-ownershipSkill
- ticket-resolutionSkill
- visitor-identificationSkill
- workflow-automationSkill
- workSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Read bulk-operations/SKILL.md first — JSONL piping, batch read, and jq reshape patterns (resources/json-patterns.md) apply.
≈ “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
Read bulk-operations/SKILL.md first — JSONL piping, batch read, and jq reshape patterns (resources/json-patterns.md) apply. hubspot activities list --help is the source of truth.
Output shape
activities list returns one flat row per activity, sorted newest-first: {id, type, timestamp, lastModified, title, body, status, owner_id}. timestamp and lastModified are ISO 8601; type is CALL|EMAIL|NOTE|MEETING|TASK. Different from the raw hs_call_* / hs_timestamp (Unix ms) on the underlying objects — fetch those with hubspot objects get --type calls if needed.
For point-in-time filtering compare lastModified (hs_lastmodifieddate, when the body was last edited), not timestamp (engagement creation time) — otherwise you include content edited after your cutoff.
All activity for a record
Pass exactly one of --contact, --deal, --company, --ticket (or --type <object_type> --record <id> for any other object type). Use --activity-type CALL|EMAIL|NOTE|MEETING|TASK to filter by activity kind, --limit N for the most recent N. Note --type is now the object-type flag, not the activity-kind filter:
hubspot activities list --contact 73235
hubspot activities list --deal 67890 --activity-type CALL
hubspot activities list --type subscriptions --record 45123 --activity-type NOTE
hubspot activities list --contact 73235 --limit 10Client-side date filter
ISO 8601 strings compare lexicographically.
CUTOFF=$(date -v-30d +%Y-%m-%dT%H:%M:%SZ) # macOS
# CUTOFF=$(date -u -d '30 days ago' +%Y-%m-%dT%H:%M:%SZ) # Linux
hubspot activities list --contact 73235 \
| jq -c --arg cutoff "$CUTOFF" 'select(.timestamp > $cutoff)'Compact timeline
hubspot activities list --contact 73235 --limit 20 \
| jq -r '"\(.timestamp[0:10]) \(.type) \(.title)"'Pre-call brief
Four piped commands: contact + company + open deals + activity. Use batch objects get over stdin — never xargs -I{} (see bulk-operations/SKILL.md).
cid=73235
echo "=== Contact ==="
hubspot objects get --type contacts $cid \
--properties email,firstname,lastname,phone,jobtitle,lifecyclestage --format table
echo "=== Company ==="
hubspot associations list --from contacts:$cid --to companies \
| jq -c '{id}' \
| hubspot objects get --type companies --properties name,domain,industry,annualrevenue --format table
echo "=== Open Deals ==="
hubspot associations list --from contacts:$cid --to deals \
| jq -c '{id}' \
| hubspot objects get --type deals --properties dealname,amount,dealstage,closedate,hs_is_closed \
| jq -c 'select(.properties.hs_is_closed != "true")'
echo "=== Recent Activity ==="
hubspot activities list --contact $cid --limit 10 \
| jq -r '"\(.timestamp[0:10]) \(.type) \(.title)"'Transcripts
Fetch the transcript for a single call or meeting by its activity ID (from hubspot activities list). Defaults to CALL; pass --activity-type MEETING for a meeting, and --fields to limit which enrichment fields are fetched:
hubspot activities transcript get 54321
hubspot activities transcript get 54321 --activity-type MEETING
hubspot activities transcript get 54321 --fields recordingUrl,aiSummaryDump all call transcripts to a file:
hubspot objects list --type calls --limit 100 --properties hs_call_title \
| jq -r '.id' \
| while read -r call_id; do
hubspot activities transcript get "$call_id"
done > /tmp/transcripts.jsonlOutput shape: {"transcriptId":"...","activityId":...,"transcriptSource":"...","transcriptStatus":"READY","numUtterances":3,"recordingUrl":"...","aiSummary":"...","transcriptionProvider":null,"utterances":[...],"createdAt":"...","updatedAt":"..."}. transcriptStatus, numUtterances, recordingUrl, aiSummary, and transcriptionProvider are the five enrichment fields — present only on enriched transcripts, and --fields limits which are fetched. The utterances array holds the speech content; empty if no transcript was recorded or uploaded.
Deleting a transcript is irreversible: hubspot activities transcript delete <id> --dry-run first, then re-run with --digest/--confirm (confirm the target name from the preview line).
Constraints
--limitdefaults to 100 and there is no--aftercursor — long histories can't be paged.bodycan be long; use the compact timeline for skimming.
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.

