executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
memos-apiHandles 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, o…
Independent GitHub snapshot · Automated classification · Original documentation governs
pageSize, pageToken, and filter (AIP-160) if available.updateMask=field1,field2 when partial updates are supported.requests snippet.references/memos-api-reference.md.curl -s -H "Authorization: Bearer $MEMOS_TOKEN" \
"$MEMOS_BASE/api/v1/memos?pageSize=20"
curl -s -X POST -H "Content-Type: application/json" \
-H "Authorization: Bearer $MEMOS_TOKEN" \
"$MEMOS_BASE/api/v1/memos" \
-d '{"content":"hello"}'
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"}'
curl -s -H "Authorization: Bearer $MEMOS_TOKEN" \
"$MEMOS_BASE/api/v1/attachments?pageSize=20"
references/memos-api-reference.md — full scraped API reference (all services/endpoints).$MEMOS_BASE, $MEMOS_TOKEN, $MEMO_ID) and avoid leaking secrets.curl -s and JSON bodies; add headers only as required.