agentleFS
OpenMinisOpenMinis/MinisSkills/memos-api/SKILL.md

memos-api

Skill584 starsChanged 59 days agoMITView on GitHub

Handles Memos API usage: crafting curl/python requests with Authorization Bearer tokens, paginating with pageSize/pageToken, using filter (AIP-160 syntax), updateMask updates, and mapping common endpoints (memo CRUD, attachments, activities, auth, identity providers). Trigger when user asks to call/inspect/troubleshoot Memos API, generate sample requests, or batch download memos. Warn to avoid printing tokens.

  • Sends data out

We split this skill into the rules it gives an agent

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

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If user needs full endpoint details, load reference file references/memos-api-reference.md.

    line 20
  2. Distinctive:

    Keep responses concise; link to reference when detailed schemas are needed.

    line 52
  3. Very specific:

    Use placeholders/env vars ($MEMOS_BASE, $MEMOS_TOKEN, $MEMO_ID) and avoid leaking secrets.

    line 53
  4. Very specific:

    Prefer curl -s and JSON bodies.

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Memos API Skill

When to use

  • User wants to call Memos API, build curl/python examples, or debug responses
  • Needs memo CRUD, attachments, activities, auth/identity providers, or list/filter/pagination
  • Needs batch download scripts or reference docs for endpoints

How to use

  1. Require base URL and bearer token (env var recommended). Do not print secret values.
  2. For list endpoints: support pageSize, pageToken, and filter (AIP-160) if available.
  3. For updates: use updateMask=field1,field2 when partial updates are supported.
  4. Return ready-to-run curl examples; optionally include python requests snippet.
  5. If user needs full endpoint details, load reference file references/memos-api-reference.md.

Quick curl templates

  • List memos (example):
    curl -s -H "Authorization: Bearer $MEMOS_TOKEN" \
         "$MEMOS_BASE/api/v1/memos?pageSize=20"
  • Create memo:
    curl -s -X POST -H "Content-Type: application/json" \
         -H "Authorization: Bearer $MEMOS_TOKEN" \
         "$MEMOS_BASE/api/v1/memos" \
         -d '{"content":"hello"}'
  • Update memo (partial):
    curl -s -X PATCH -H "Content-Type: application/json" \
         -H "Authorization: Bearer $MEMOS_TOKEN" \
         "$MEMOS_BASE/api/v1/memos/$MEMO_ID?updateMask=content" \
         -d '{"content":"updated"}'
  • List attachments:
    curl -s -H "Authorization: Bearer $MEMOS_TOKEN" \
         "$MEMOS_BASE/api/v1/attachments?pageSize=20"

Bundled references

  • references/memos-api-reference.md — full scraped API reference (all services/endpoints).

Notes

  • Keep responses concise; link to reference when detailed schemas are needed.
  • Use placeholders/env vars ($MEMOS_BASE, $MEMOS_TOKEN, $MEMO_ID) and avoid leaking secrets.
  • Prefer curl -s and JSON bodies; add headers only as required.

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.

Reviews can't be read right now.

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.