agentleFS
Sign inStart free
thenslsthensls/nsls-builder-toolkit/skills/hubspot/SKILL.md

hubspot

Skill0 starsChanged 3 days agoNo licenceView on GitHub

Query NSLS HubSpot CRM — 6.9M contacts, 340K deals, 357K tickets, 11K companies. Search members by chapter/school/status, look up enrollment history, check induction milestones, explore chapter health, investigate support tickets. NSLS syncs from Feather (legacy platform) with rich custom properties. Read-only access. Trigger phrases: hubspot, CRM, member lookup, chapter, enrollment, induction, IPEDS, school data, deal pipeline, ticket, support history, member status, who enrolled, chapter health.

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use discord and jira.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • jiulingyunSkill

    discord

    Discord ops via the message tool (channel=discord).

    Also in 3 projects that use this

  • MicrosoftSkill

    jira

    Jira issue workflows for search, issue updates, transitions, comments, field discovery, and interactive credential setup via the Jira REST API. Use when you need to configure Jira access, search with JQL, inspect an issue, create or update work items, move an issue between statuses, post comments, or discover required fields for issue creation.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 1 is distinctive, and 10 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 10

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free