agentleFS
systemind-teamsystemind-team/AICOO-Skills/skills/invite-team/SKILL.md

invite-team

Skill35 starsChanged 4 months agoMITView on GitHub

Use this skill when the user wants to invite teammates to Aicoo — generate a team invite link, or a copy-paste prompt that sets a teammate up automatically. Triggers on: 'invite my team', 'invite a teammate', 'add team members', 'invite someone to my team', 'team invite link', 'onboard my team', 'get my coworkers on Aicoo', 'generate an invite'.

  • Reads credentials
  • Sends data out

The file

Files
SKILL.md

Invite Team — Two Ways To Bring People In

Offer both and let the user pick per person:

  • Copy-paste onboarding prompt — best for technical teammates. A block they paste into their own Claude Code / Codex / agent runtime that installs the skills, signs them in, builds their memory, and connects them back. Works for anyone, needs no Team plan.
  • Invite link — best for anyone with (or willing to make) an Aicoo account. Adds them to your Team plan's seats. Requires you to own/admin a Team plan and the os.team:write scope.

Requires being signed in (onboarding skill). Resolve the token with the pack's scripts/aicoo-auth.sh: export AICOO_API_KEY="$(bash /path/to/aicoo-skills/scripts/aicoo-auth.sh)".


A) Copy-paste onboarding prompt (always available)

Get the inviter's username, then hand the user a ready-to-share block.

curl -s "https://www.aicoo.io/api/v1/identity" \
  -H "Authorization: Bearer $AICOO_API_KEY" | jq -r '.identity.username // .profile.username'

Present exactly this (substitute <username>; if you also made an invite link in section B, add it as an optional line):

Send this to your teammate — they paste it into their AI agent (Claude Code, Codex, …):

---
Set me up on Aicoo and connect me to my teammate.

1. Install the Aicoo skills:
   npx skills add Aicoo-Team/AICOO-Skills
   (or: git clone https://github.com/Aicoo-Team/AICOO-Skills.git ~/.claude/plugins/aicoo-skills)
2. Sign in with Aicoo:
   node ~/.claude/plugins/aicoo-skills/scripts/aicoo-login.mjs
3. Run the Aicoo onboarding skill to build my agent memory and share my agent.
4. Connect me to @<username> on Aicoo (accept their team invite if I have one).
---

The teammate's agent does the install → sign-in → onboarding → connect end to end. Nothing else needed from you.

B) Invite link (Team plan)

B1. Check team status first

curl -s "https://www.aicoo.io/api/v1/os/team" \
  -H "Authorization: Bearer $AICOO_API_KEY" \
  | jq '{hasTeam, role, canInvite, seatsAvailable: .team.seatsAvailable, members: (.members|length), pendingInvites}'

Handle the outcome:

  • hasTeam:false → not on a Team plan. Point to https://www.aicoo.io/settings/team to start one (from $30/seat, 3 seats min). Then use section A in the meantime.
  • canInvite:false → they're a member, not owner/admin. Only owners/admins invite — use section A instead.
  • seatsAvailable:0 → all seats used. Add seats at https://www.aicoo.io/settings/team.

B2. Create the invite

Reusable link (anyone can use it until seats fill) — omit email:

curl -s -X POST "https://www.aicoo.io/api/v1/os/team/invite" \
  -H "Authorization: Bearer $AICOO_API_KEY" -H "Content-Type: application/json" \
  -d '{"role":"member"}' | jq '{inviteUrl, emailDelivered}'

Email a specific person (also emails them the link if transactional email is configured; still returns inviteUrl for you to share directly):

curl -s -X POST "https://www.aicoo.io/api/v1/os/team/invite" \
  -H "Authorization: Bearer $AICOO_API_KEY" -H "Content-Type: application/json" \
  -d '{"email":"teammate@company.com","role":"member"}' | jq '{inviteUrl, emailDelivered}'

role may be member or admin. Present the returned https://www.aicoo.io/team/invites/<token> — the recipient accepts by opening it while signed in to Aicoo.

B3. Best experience — pair both

Send the invite link (joins your team) together with the section-A prompt (sets up their own agent). Link alone only adds a seat; the prompt is what actually gets their agent built and connected.


Notes & errors

ResultMeaning / action
403 insufficient_scopeLogin didn't grant os.team:write — re-run aicoo-login.mjs to re-consent
404 / hasTeam:falseNot on a Team plan → /settings/team, or use the section-A prompt
403 "owners and admins"You're a member; use the section-A prompt
409 seats in useAdd seats at /settings/team
429Rate-limited (20 invites/min) — wait a moment
  • The invite link is reusable until seats fill; revoke pending invites at https://www.aicoo.io/settings/team.
  • Teams are a billing/seat + entitlement grouping. To share content with the team (a knowledge base), use a folder-scoped share link — see the share-agent and onboarding skills.

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.