memos
Skill2 starsChanged 8 months agoMITView on GitHub
Interact with Memos API to create, read, update, and delete memos, manage users and attachments, handle authentication, and configure instance settings. Use when the user wants to work with a Memos instance, create notes, manage content, or perform administrative tasks. Requires MEMOS_URL and MEMOS_TOKEN environment variables or user-provided credentials.
- Reads credentials
- Sends data out
4 other projects use a version of this.
Adopted by
Most recently taken up by
- tnnevol/skillstheir own version, first seen Nov 8, 2026
- jtsang4/efficient-codingtheir own version, first seen Sep 12, 2026
- alumpe/skillstheir own version, first seen Sep 11, 2026
- akhy/agent-skillstheir own version, first seen Mar 4, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- jtsang4/efficient-coding★ 2same name
- akhy/agent-skills★ 1same name
- tnnevol/skills★ 1same name
- alumpe/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
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
- Distinctive: line 19
Before using this skill, ensure you have:
- Distinctive: line 156
All errors follow this format:
- Very specific: line 185
All endpoints use the base path: /api/v1
- Very specific: line 191
All authenticated endpoints require the Authorization header:
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Memos API Skill
Interact with a Memos instance through its REST API.
Prerequisites
Before using this skill, ensure you have:
- MEMOS_URL: The base URL of your Memos instance (e.g.,
http://localhost:5230orhttps://memos.example.com) - MEMOS_TOKEN: A Personal Access Token for authentication
Obtaining a Personal Access Token
- Log in to your Memos instance
- Navigate to Settings → My Account → Access Tokens
- Click Create Access Token
- Provide a description (e.g., "AI Agent Token")
- Set expiration as needed (or leave empty for no expiration)
- Copy the generated token immediately - it is shown only once
Store the token securely. For local development, set environment variables:
export MEMOS_URL="http://localhost:5230"
export MEMOS_TOKEN="your-personal-access-token"Quick Reference
| Service | Description | Key Operations |
| Memo | Notes and content | Create, List, Get, Update, Delete, Comments, Reactions |
| User | User management | Create, Get, List, Update, Delete, Personal Access Tokens |
| Auth | Authentication | Sign in, Sign out, Refresh token, Current user |
| Attachment | Files and media | Create, Get, List, Update, Delete |
| Shortcut | Saved filters | Create, Get, List, Update, Delete |
| Instance | Server settings | Get profile, Get/Update settings |
Common Operations
Create a Memo
Request:
curl -X POST "${MEMOS_URL}/api/v1/memos" \
-H "Authorization: Bearer ${MEMOS_TOKEN}" \
-H "Content-Type: application/json" \
-d '{
"content": "# My First Memo\n\nThis is the content of my memo.",
"visibility": "PRIVATE"
}'JavaScript:
const response = await fetch(`${process.env.MEMOS_URL}/api/v1/memos`, {
method: 'POST',
headers: {
'Authorization': `Bearer ${process.env.MEMOS_TOKEN}`,
'Content-Type': 'application/json'
},
body: JSON.stringify({
content: '# My First Memo\n\nThis is the content of my memo.',
visibility: 'PRIVATE'
})
});
const memo = await response.json();Response:
{
"name": "memos/abc123",
"state": "NORMAL",
"creator": "users/1",
"createTime": "2024-01-15T10:30:00Z",
"content": "# My First Memo\n\nThis is the content of my memo.",
"visibility": "PRIVATE"
}List Memos
Request:
curl -X GET "${MEMOS_URL}/api/v1/memos?pageSize=10" \
-H "Authorization: Bearer ${MEMOS_TOKEN}"JavaScript:
const response = await fetch(`${process.env.MEMOS_URL}/api/v1/memos?pageSize=10`, {
headers: { 'Authorization': `Bearer ${process.env.MEMOS_TOKEN}` }
});
const { memos } = await response.json();Get a Single Memo
Request:
curl -X GET "${MEMOS_URL}/api/v1/memos/{memoId}" \
-H "Authorization: Bearer ${MEMOS_TOKEN}"Update a Memo
Request:
curl -X PATCH "${MEMOS_URL}/api/v1/memos/{memoId}?updateMask=content,visibility" \
-H "Authorization: Bearer ${MEMOS_TOKEN}" \
-H "Content-Type: application/json" \
-d '{
"content": "Updated content",
"visibility": "PUBLIC"
}'Delete a Memo
Request:
curl -X DELETE "${MEMOS_URL}/api/v1/memos/{memoId}" \
-H "Authorization: Bearer ${MEMOS_TOKEN}"Visibility Values
| Value | Description |
PRIVATE | Only visible to the creator |
PROTECTED | Visible to logged-in users |
PUBLIC | Visible to everyone |
State Values
| Value | Description |
NORMAL | Active memo |
ARCHIVED | Archived memo |
Error Handling
All errors follow this format:
{
"code": 3,
"message": "Invalid argument",
"details": []
}See error-codes.md for common error codes and resolution strategies.
Detailed Documentation
For comprehensive API documentation:
- Full API Reference
- Memo Operations
- User Management
- Authentication
- Attachments
- Advanced Features
Helper Scripts
Executable scripts are available in the scripts/ directory:
memos-api.sh- Bash helper functionsmemos-client.js- JavaScript client library
API Base URL
All endpoints use the base path: /api/v1
Example: http://localhost:5230/api/v1/memos
Authentication
All authenticated endpoints require the Authorization header:
Authorization: Bearer YOUR_ACCESS_TOKENPagination
List endpoints support pagination:
pageSize: Maximum items per page (default: 50, max: 1000)pageToken: Token from previous response for next page
Filtering
Some list endpoints support filtering via the filter parameter using Google AIP-160 syntax:
filter=row_status == "NORMAL"
filter=visibility == "PUBLIC"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
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.

