Individual skill
aai-hubspot
Use aai-cli to inspect HubSpot CRM records, files, events, conversations, visitor identification, and custom channels.
api/domains/agents/aai_cli_skills/bundled/skills/aai-hubspot/SKILL.md
Source commit 724a8ace26035d19f64cc707fbc0b4ba110cbc95
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 111
- Repository last updated
- Nov 9, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent Repository topic
- agent-skills Repository topic
- agentic-ai Repository topic
- helm Repository topic
- helm-charts Repository topic
- kubernetes Repository topic
- python Repository topic
- cli Repository topic
- cli-tool Repository topic
- sales Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 892 bytesreferences/command-reference.mddoc · 2,266 bytes
Read excerpt
# aai-cli HubSpot
Use this skill when working with HubSpot through `aai-cli hubspot`.
Before running commands, confirm the active profile or pass `--profile`. HubSpot profiles use `auth_type = "hubspot_service_key"` or `auth_type = "hubspot_legacy_private_app"` with `token_secret`.
HubSpot `401` and `403` errors include scope and auth-model remediation under `details`. Preserve that JSON when reporting failures. Custom channel commands are not supported for legacy private app tokens and return `unsupported_auth` before making a request.
Successful output is JSON on stdout. Errors are structured JSON on stderr. See [the command reference](references/command-reference.md) for command shapes, scopes, and failure handling.