agentleFS
iblaiiblai/higher-education-agents/skills/slate/SKILL.md

slate

Skill14 starsChanged 5 months agoMITView on GitHub

Technolutions Slate CRM — lets an agent read and write prospect, applicant, and admitted-student records and trigger enrollment communication workflows.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never write directly to the source-of-record application fields without institutional approval.

    line 33
  2. Very specific:

    Test environment is a separate Slate instance.

    line 34

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Slate

What it is

Slate by Technolutions is the dominant CRM and admissions platform in higher education. It manages the full enrollment funnel from first inquiry through enrollment confirmation: prospect capture, application review, communications, event registrations, and yield tracking. It is used by enrollment, application-reader, prospective-student, and yield agents.

When to use this skill

  • Capturing a new prospect's contact info and program interest from a chatbot conversation
  • Retrieving a complete application record including essays, test scores, and recommendations
  • Logging yield outreach interactions and updating a student's decision stage
  • Querying segment lists for targeted communication campaigns
  • Pulling cohort statistics for percentile benchmarking during application review

Credentials

This skill authenticates using env vars declared in the frontmatter metadata field. Set these in ~/.openclaw/.env (template: .env.example):

  • SLATE_BASE_URL - institution's Slate instance URL (e.g. https://apply.university.edu)
  • SLATE_API_KEY - Slate REST API key issued under Configuration > API

Key operations

  • POST /manage/query/run — execute a saved Slate query to retrieve prospect or applicant record sets
  • POST /manage/service/ — write interaction records, update field values, and advance funnel stage
  • GET /manage/lookup/query — resolve a person record by email or student ID
  • POST /manage/export/ — bulk export applicant data for cohort benchmarking
  • Webhook inbound: Slate can push application status change events to the agent endpoint

Notes

  • Slate's API is query-based rather than RESTful resource-based; most reads use the Query endpoint with a saved query GUID.
  • Never write directly to the source-of-record application fields without institutional approval; use interaction/note records for agent-generated data.
  • Test environment is a separate Slate instance; configure SLATE_BASE_URL accordingly for sandbox testing.
  • FERPA applies to all applicant data; limit field retrieval to only the fields the agent's task requires.

Download now (ZIP)

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.