skills/bear-notes/SKILL.md
Create, search, and manage Bear notes via grizzly CLI.
npx skillsauth add openclaw/openclaw bear-notesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use grizzly to create, read, and manage notes in Bear on macOS.
Requirements
~/.config/grizzly/token)For operations that require a token (add-text, tags, open-note --selected), you need an authentication token:
echo "YOUR_TOKEN" > ~/.config/grizzly/tokenCreate a note
echo "Note content here" | grizzly create --title "My Note" --tag work
grizzly create --title "Quick Note" --tag inbox < /dev/null
Open/read a note by ID
grizzly open-note --id "NOTE_ID" --enable-callback --json
Append text to a note
echo "Additional content" | grizzly add-text --id "NOTE_ID" --mode append --token-file ~/.config/grizzly/token
List all tags
grizzly tags --enable-callback --json --token-file ~/.config/grizzly/token
Search notes (via open-tag)
grizzly open-tag --name "work" --enable-callback --json
Common flags:
--dry-run — Preview the URL without executing--print-url — Show the x-callback-url--enable-callback — Wait for Bear's response (needed for reading data)--json — Output as JSON (when using callbacks)--token-file PATH — Path to Bear API token fileGrizzly reads config from (in priority order):
GRIZZLY_TOKEN_FILE, GRIZZLY_CALLBACK_URL, GRIZZLY_TIMEOUT).grizzly.toml in current directory~/.config/grizzly/config.tomlExample ~/.config/grizzly/config.toml:
token_file = "~/.config/grizzly/token"
callback_url = "http://127.0.0.1:42123/success"
timeout = "5s"
--enable-callback when you need to read data back from Beardevelopment
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
data-ai
Example TaskFlow authoring pattern for inbox triage. Use when messages need different treatment based on intent, with some routes notifying immediately, some waiting on outside answers, and others rolling into a later summary.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------