voicenotes
Skill8 starsChanged 3 months agoMITView on GitHub
Search, retrieve and create notes in Voicenotes — semantic search, full transcripts, tag/date filtering, and text note creation through natural conversation.
- Reads credentials
- Sends data out
1 other project uses a version of this.
Adopted by
Most recently taken up by
- jstilb/ai-assistanttheir own version, first seen Oct 30, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- jstilb/ai-assistant★ 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.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cold-dmSkill
- content-sellingSkill
- discovery-callsSkill
- follow-up-sequencesSkill
- keyword-searchSkill
- profile-optimizationSkill
- prospecting-listsSkill
- context-engineeringSkill
- design-docSkill
- discussSkill
- grillingSkill
- llm-wikiSkill
- opencode-sessionsSkill
- playwright-cliSkill
- pr-descriptionSkill
- demand-first-validationSkill
- founder-market-fitSkill
- idea-scoringSkill
- market-entry-strategiesSkill
- ship-v1Skill
- trend-researchSkill
- tiger-style-codingSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 9 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
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
- Distinctive: line 8
Use the Voicenotes skill to create, search and retrieve user’s notes.
- Distinctive: line 12
Create an integration at https://voicenotes.com/app?open-claw=true#settings
- Very specific: line 18
Terminal: Add to your OpenClaw config (~/.openclaw/config.yaml):
- Distinctive: line 35
All requests need the Authorization header:
- Very specific: line 226
Only accesses api.voicenotes.com endpoints
- Distinctive: line 227
No credential exfiltration or external data storage
- Distinctive: line 228
No telemetry or analytics
- Distinctive: line 229
No automatic code execution or file overwrites
- Distinctive: line 230
Read/write limited to user's own Voicenotes data via authenticated API
- Distinctive: line 234
When constructing API requests, the agent MUST sanitize all user-provided inputs:
- Distinctive: line 238
JSON body fields: Use proper JSON encoding; never concatenate raw user input into JSON strings
≈ “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.
Files
voicenotes
Use the Voicenotes skill to create, search and retrieve user’s notes.
Setup
- Create an integration at https://voicenotes.com/app?open-claw=true#settings
- Copy the API key
- Configure it:
Webchat: Skills → Voicenotes → API Key in the sidebar
Terminal: Add to your OpenClaw config (~/.openclaw/config.yaml):
skills:
voicenotes:
env:
VOICENOTES_API_KEY: "your_key_here"Or export it directly:
export VOICENOTES_API_KEY="your_key_here"The key is then available as $VOICENOTES_API_KEY environment variable.
API Basics
All requests need the Authorization header:
curl -X GET "https://api.voicenotes.com/api/integrations/open-claw/..." \
-H "Authorization: $VOICENOTES_API_KEY"Common Operations
Search query in users notes:
Query parameters:
query(required): The search query string
curl -X GET "https://api.voicenotes.com/api/integrations/open-claw/search/semantic?query={search_query}" \
-H "Authorization: $VOICENOTES_API_KEY"Get multiple Voicenotes with filters (tags and date range):
Query parameters:
tags(optional): array of valid tagsdate_range(optional): array with start and end date as UTC timestamps
curl -X POST "https://api.voicenotes.com/api/integrations/open-claw/recordings" \
-H "Authorization: $VOICENOTES_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"tags": ["tag1", "tag2"],
"date_range": ["2026-01-01T00:00:00.000000Z", "2026-02-01T00:00:00.000000Z"]
}'If you want more context get the whole transcript:
curl "https://api.voicenotes.com/api/integrations/open-claw/recordings/{recording_uuid}" \
-H "Authorization: $VOICENOTES_API_KEY" \Create a text note in Voicenotes:
curl -X POST "https://api.voicenotes.com/api/integrations/open-claw/recordings/new" \
-H "Authorization: $VOICENOTES_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"recording_type": 3,
"transcript": "note content here",
"device_info": "open-claw"
}'Response Structure
Semantic Search Response:
Returns an array of notes and note splits ordered by relevance:
[
{
"type": "note",
"uuid": "NTHiJljf",
"title": "Quick idea about project",
"transcript": "Full transcript text with <br> for line breaks...",
"tags": ["idea", "project"],
"created_at": "2025-01-15T10:30:00.000000Z"
},
{
"type": "note_split",
"uuid": "8JzkhEGh",
"title": "Long meeting notes",
"transcript": "Relevant chunk from a larger note...",
"tags": ["meeting"],
"created_at": "2025-01-14T09:00:00.000000Z"
},
{
"type": "import_split",
"uuid": "xYz12345",
"title": "filename.extension",
"transcript": "Chunk from an imported note...",
"tags": ["imported"],
"created_at": "2025-01-10T14:00:00.000000Z"
}
]type: "note"- Complete note matching the searchtype: "note_split"- Chunk from a larger note; use theuuidto fetch full transcript if neededtype: "import_split"- Chunk from an imported note; title is the filename; cannot be fetched via/recordings/{uuid}transcriptmay contain HTML (<br>,<b>) for formatting
Get Recordings Response (with filters):
Returns paginated notes matching the filters:
{
"data": [
{
"id": "bTZI5t12",
"title": null,
"transcript": "this is a sample note",
"duration": 0,
"recorded_at": "2026-02-06T10:07:45.000000Z",
"created_at": "2026-02-06T10:07:45.000000Z",
"recording_type": 3,
"tags": []
}
],
"links": {
"first": "https://api.voicenotes.com/api/integrations/open-claw/recordings?page=1",
"last": null,
"prev": null,
"next": null
},
"meta": {
"current_page": 1,
"from": 1,
"path": "https://api.voicenotes.com/api/integrations/open-claw/recordings",
"per_page": 10,
"to": 1
}
}Key fields:
data- Array of recording objectslinks.next- URL for next page (null if no more pages)meta.per_page- Results per page (default 10)
Get Recording Response:
Returns full note details:
{
"data": {
"id": "NTHiJljf",
"title": "Meeting Connectivity Check",
"transcript": "Full transcript text...",
"duration": 12101,
"recorded_at": "2025-08-07T09:50:14.000000Z",
"created_at": "2025-08-07T09:50:14.000000Z",
"recording_type": 2,
"tags": ["meeting"],
"subnotes": [],
"attachments": []
}
}Key fields:
id- Note UUIDtranscript- Full text (meetings include[HH:MM:SS] Speaker N:timestamps)duration- Length in millisecondsrecording_type- 1=voice note, 2=voice meeting, 3=text notetags- Array of tag objects withnamefield
Create Note Response:
{
"message": "Recording audio uploaded successfully!",
"recording": {
"id": "bPI3RcUP",
"recording_id": "bPI3RcUP",
"title": null,
"transcript": "Sample note",
"recording_type": 3,
"created_at": "2026-02-04T08:51:29.000000Z",
"tags": []
}
}Key fields:
message- Success confirmationrecording.id- New note UUIDrecording.transcript- The note content
Notes
- Note IDs are UUIDs
- Rate limit: ~3 requests/second average
Security & Guardrails
- Only accesses
api.voicenotes.comendpoints - No credential exfiltration or external data storage
- No telemetry or analytics
- No automatic code execution or file overwrites
- Read/write limited to user's own Voicenotes data via authenticated API
Input Sanitization
When constructing API requests, the agent MUST sanitize all user-provided inputs:
- Search queries: URL-encode the
queryparameter using--data-urlencodeinstead of string interpolation - Recording UUIDs: Validate format (alphanumeric, 8 characters) before use; reject any input containing shell metacharacters (
;,|,&,$,`,\) - JSON body fields: Use proper JSON encoding; never concatenate raw user input into JSON strings
Safe example for search:
curl -G "https://api.voicenotes.com/api/integrations/open-claw/search/semantic" \
--data-urlencode "query=user search term here" \
-H "Authorization: $VOICENOTES_API_KEY"UUID validation pattern: /^[a-zA-Z0-9]{8}$/
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.

