claudeaceae/.claude/skills/decide
.claude/skills/decide/SKILL.md
--- name: decide description: Document a decision with rationale and alternatives considered. Use when making a choice, recording why something was decided, capturing trade-offs, or logging architectural decisions. Trigger words: decide, decision, chose, choice, why did we, trade-off, ADR. --- # Decision Documentation Capture decisions with full context for future reference. ## Decision Record Format ```markdown ## YYYY-MM-DD: [Decision Title] ### Context What situation or problem prompted
$ install --global
skillsauthnpx skillsauth add claudeaceae/samara-main .claude/skills/decideInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 8:50 PM1.8s1 file scanned
SKILL.md
- name:
- decide
- description:
- Document a decision with rationale and alternatives considered. Use when making a choice, recording why something was decided, capturing trade-offs, or logging architectural decisions. Trigger words: decide, decision, chose, choice, why did we, trade-off, ADR.
Decision Documentation
Capture decisions with full context for future reference.
Decision Record Format
## YYYY-MM-DD: [Decision Title]
### Context
What situation or problem prompted this decision?
### Decision
What was decided?
### Alternatives Considered
1. **[Alternative 1]**: [Brief description]
- Pros: ...
- Cons: ...
2. **[Alternative 2]**: [Brief description]
- Pros: ...
- Cons: ...
### Rationale
Why was this option chosen over the alternatives?
### Expected Outcome
What do we expect to happen as a result?
### Review Date (optional)
When should this decision be revisited?
Process
-
Gather context: What's the decision about? What prompted it?
-
List alternatives: What options were considered?
-
Capture rationale: Why this choice? What trade-offs were accepted?
-
Record expected outcome: What should happen if this is the right call?
-
Append to decisions.md:
# Append the formatted decision to the decisions file
~/.claude-mind/memory/decisions.md
Guidelines
- Be specific about the context - future-you won't remember
- Include alternatives even if they were quickly dismissed
- Capture the "why" more than the "what"
- Note any assumptions that might change
- Link to related decisions if applicable
Example
## 2025-01-04: Use AppleScript over MCP for Mac Apps
### Context
Need to interact with Calendar, Contacts, Notes from Claude Code.
### Decision
Use direct AppleScript via osascript instead of MCP servers.
### Alternatives Considered
1. **MCP Servers**: Structured API, abstraction layer
- Pros: Clean interface, type safety
- Cons: Extra process, permission issues, often read-only
2. **AppleScript Direct**: Shell out to osascript
- Pros: Full control, reliable, no extra dependencies
- Cons: Verbose syntax
### Rationale
MCP is designed for "Claude visiting" - sandboxed access. We're "Claude as resident" with FDA. The abstraction solves a different problem.
### Expected Outcome
More reliable automation, fewer permission issues, simpler debugging.
Quick Capture
For rapid decision logging, minimum viable format:
## YYYY-MM-DD: [Title]
**Decision**: [What]
**Why**: [Rationale]
**Trade-off**: [What we gave up]
Related Skills
claudeaceae/.claude/skills/webhook
development
VerifiedTrustedCommunity
# /webhook --- name: webhook description: Manage webhook sources - list, add, test, and view incoming events context: fork triggers: - webhook - add webhook - create webhook - webhook setup - incoming webhooks --- Manage the webhook receiver system. Use this skill to add new webhook sources, test existing ones, and view incoming events. ## What You Can Do 1. **List sources** - Show all registered webhook sources 2. **Add source** - Create a new webhook source with secure secret 3.
9SKILL.mdUpdated Apr 16, 2026
claudeaceae/wallet
testing
VerifiedTrustedCommunity
Check crypto wallet balances, transaction history, and addresses
9SKILL.mdUpdated Apr 16, 2026
claudeaceae/.claude/skills/voice-call
testing
VerifiedTrustedCommunity
# /voice-call - FaceTime Voice Calling Place and receive FaceTime Audio calls with live transcription and voice/text responses. ## Quick Start ```bash # Full voice conversation (responds via FaceTime audio) ~/.claude-mind/system/bin/voice-call --voice-response # Call with text responses (via iMessage) ~/.claude-mind/system/bin/voice-call --text-response # Call a specific number ~/.claude-mind/system/bin/voice-call +15551234567 --voice-response ``` ## Prerequisites Run `audio-setup --check
9SKILL.mdUpdated Apr 16, 2026
claudeaceae/.claude/skills/sync
tools
VerifiedTrustedCommunity
--- name: sync description: Check for drift between repo and running system. Use when checking if scripts or Samara are out of sync, verifying system integrity, or before/after rebuilds. Trigger words: sync, organism sync, check drift, system drift, repo sync. context: fork allowed-tools: - Bash - Read - Grep --- # Sync Skill Check for drift between the repo and running system, and optionally fix it. ## What This Does Runs the `sync-organism` script to detect differences between: - `~/
9SKILL.mdUpdated Apr 16, 2026