agentleFS
Sign inStart free
cobusgreylingcobusgreyling/grok-bot-templates/skills/ramp-new-hire/SKILL.md

ramp-new-hire

Skill14 starsChanged 3 months agoMITView on GitHub

Paste this into Grok Bot after a successful run: Save the process we just used as a skill called “Ramp New Hire”. A useful skill states the six fields from Skills and routines. A named new hire starts soon and needs a first-week plan with owners and calendar holds as drafts — invites stay unsent. Every session has a named owner. No invites were sent. No Slack messages were sent. Unknown owners are labeled unknown, not filled with the manager.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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
  1. Distinctive:

    Write the plan to /workspace/new-hire-ramp.md.

    line 26
  2. Distinctive:

    Every session has a named owner.

    line 30
  3. Distinctive:

    Do not send calendar invites.

    line 40

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

Ramp New Hire

Paste this into Grok Bot after a successful run:

Save the process we just used as a skill called “Ramp New Hire”.

A useful skill states the six fields from Skills and routines.

1. When to use it

A named new hire starts soon and needs a first-week plan with owners and calendar holds as drafts — invites stay unsent.

2. Required inputs and access

  • Hire name, role, start date, and manager
  • Team roster or org notes the owner attached
  • Google Calendar and approved Slack channels

3. Sequence of work

  1. Confirm name, start date, role, and manager. If any are missing, ask and stop.
  2. Draft a day-by-day first-week plan with session, owner, purpose, and the Slack or doc they need.
  3. Draft calendar holds for each session. Do not invite anyone.
  4. Build a share checklist (channels, docs). Do not send Slack DMs or channel posts.
  5. Write the plan to /workspace/new-hire-ramp.md.

4. How to validate the result

Every session has a named owner. No invites were sent. No Slack messages were sent. Unknown owners are labeled unknown, not filled with the manager.

5. What to return

First-week plan, draft holds, onboarding checklist, action log.

6. What requires approval

Do not send calendar invites. Do not message the hire or the team. Do not create accounts or grant access.

Type / in the composer to reference a saved skill. If it does not appear, open Settings → Plugins → Yours and enable it for this Bot.

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.

Check your setup, free