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

start-aicoo

Skill35 starsChanged 4 months agoMITView on GitHub

Use this skill when the user wants to boot their Aicoo agent, verify identity, check workspace health, and incrementally sync new or changed context. Triggers on: 'start aicoo', 'boot my agent', 'launch aicoo', 'wake up aicoo', 'aicoo status', 'is my agent running', 'sync context', 'incremental sync', 'update my agent context', 'refresh agent knowledge'.

  • Reads credentials
  • Sends data out

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If this fails, the API key is invalid or expired — guide user to https://www.aicoo.io/settings/api-keys.

    line 24
  2. Very specific:

    If any of memory/self/COO.md, memory/self/USER.md, or memory/self/POLICY.md are missing, prompt the user to create them or offer to …

    line 44
  3. Very specific:

    If no /tmp/.aicoo-last-sync marker exists, this is a first sync — list all candidate files and ask the user which ones to include.

    line 59
  4. Distinctive:

    If a matching note exists: snapshot it, then PATCH with updated content.

    line 72
  5. Distinctive:

    If no match: create a new note.

    line 73
  6. Distinctive:

    Start of a work session

    line 119
  7. Distinctive:

    After pulling new code or docs

    line 120
  8. Distinctive:

    Before sharing an agent link

    line 121

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

Start Aicoo — Boot & Incremental Context Sync

One command to verify your agent identity, check workspace health, and push any new context.

Prerequisites

  • AICOO_API_KEY environment variable must be set
  • Base URL: https://www.aicoo.io/api/v1

Workflow

Step 1: Verify identity

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

Expected response includes profile.userId, profile.username, profile.name. If this fails, the API key is invalid or expired — guide user to https://www.aicoo.io/settings/api-keys.

Step 2: Check workspace health

curl -s "https://www.aicoo.io/api/v1/os/status" \
  -H "Authorization: Bearer $AICOO_API_KEY" | jq .

Report: note count, folder count, last sync time, active share links.

Step 3: Check identity files exist

curl -s -X POST "https://www.aicoo.io/api/v1/os/notes/search" \
  -H "Authorization: Bearer $AICOO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"COO.md USER.md POLICY.md"}' | jq .

If any of memory/self/COO.md, memory/self/USER.md, or memory/self/POLICY.md are missing, prompt the user to create them or offer to generate defaults.

Step 4: Detect local changes for incremental sync

Scan the current project directory for recently modified files:

# Find markdown/text files changed in the last 24 hours
find . -maxdepth 3 \( -name "*.md" -o -name "*.txt" \) \
  -not -path "*/node_modules/*" \
  -not -path "*/.git/*" \
  -not -path "*/.next/*" \
  -newer /tmp/.aicoo-last-sync 2>/dev/null | head -30

If no /tmp/.aicoo-last-sync marker exists, this is a first sync — list all candidate files and ask the user which ones to include.

Step 5: Search before creating (dedup)

For each file to sync, search for existing notes:

curl -s -X POST "https://www.aicoo.io/api/v1/os/notes/search" \
  -H "Authorization: Bearer $AICOO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"[file title or topic]"}' | jq .
  • If a matching note exists: snapshot it, then PATCH with updated content.
  • If no match: create a new note.

Step 6: Bulk sync changed files

curl -s -X POST "https://www.aicoo.io/api/v1/accumulate" \
  -H "Authorization: Bearer $AICOO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "files": [
      {"path": "Folder/filename.md", "content": "..."}
    ]
  }' | jq .

Step 7: Update sync marker

touch /tmp/.aicoo-last-sync

Step 8: Report summary

Print a concise status:

Aicoo Agent Status
  Identity:    @username (Name)
  Workspace:   X notes, Y folders
  Last sync:   YYYY-MM-DD HH:MM
  This sync:   N files synced (M new, K updated)
  Identity files: COO.md ✓  USER.md ✓  POLICY.md ✓
  Share links: Z active

Error Handling

ErrorAction
401 from /identityAPI key invalid — guide to settings page
Identity OK but /os/status failsWorkspace not initialized — run POST /init
Missing identity filesOffer to create defaults from user context
No local changes foundReport "Agent context is up to date"

When to Use

  • Start of a work session
  • After pulling new code or docs
  • Before sharing an agent link
  • Periodic check that agent knowledge is current

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.