07242683bf
Complete collection of AI agent skills including: - Frontend Development (Vue, React, Next.js, Three.js) - Backend Development (NestJS, FastAPI, Node.js) - Mobile Development (React Native, Expo) - Testing (E2E, frontend, webapp) - DevOps (GitHub Actions, CI/CD) - Marketing (SEO, copywriting, analytics) - Security (binary analysis, vulnerability scanning) - And many more... Synchronized from: https://skills.sh/ Co-Authored-By: Claude <noreply@anthropic.com>
80 lines
2.7 KiB
Markdown
80 lines
2.7 KiB
Markdown
# Obsidian Workflows Skill for Claude Code
|
|
|
|
A skill that integrates Claude Code with Obsidian for intelligent note management and task automation.
|
|
|
|
## Description
|
|
|
|
This skill helps you work with Obsidian vaults to:
|
|
- Create daily notes with automatic context
|
|
- Process meeting notes and extract action items
|
|
- Generate weekly reviews
|
|
- Query and manage tasks across your vault
|
|
|
|
## Configuration
|
|
|
|
Set these environment variables or update the paths below:
|
|
- `OBSIDIAN_VAULT_PATH`: Path to your Obsidian vault (default: ~/Documents/ObsidianVault)
|
|
- `DAILY_NOTES_FOLDER`: Folder for daily notes (default: "Daily Journal")
|
|
- `TASKS_FILE`: File for tracking tasks (default: "Tasks.md")
|
|
|
|
## Workflows
|
|
|
|
### Daily Note Creation
|
|
|
|
When the user asks to create a daily note:
|
|
1. Read the daily note template from the templates folder
|
|
2. Find yesterday's daily note (previous day's file in Daily Journal folder)
|
|
3. Extract any incomplete tasks from yesterday
|
|
4. Create today's note with the template, populated with:
|
|
- Today's date in YYYY-MM-DD format
|
|
- Incomplete tasks from yesterday
|
|
- Context from recent work (check recent files this week)
|
|
|
|
### Meeting Notes Processing
|
|
|
|
When the user asks to process meeting notes:
|
|
1. Read the specified meeting notes file
|
|
2. Extract action items, decisions, and discussion points
|
|
3. Format action items as Obsidian Tasks with due dates
|
|
4. Append to the tasks file with proper formatting: `- [ ] Task text 📅 YYYY-MM-DD #tag`
|
|
5. Create a summary of the meeting
|
|
|
|
### Weekly Review Generation
|
|
|
|
When the user asks to generate a weekly review:
|
|
1. Find all daily notes from the current week (Monday to Sunday)
|
|
2. Summarize work done from each day
|
|
3. List completed tasks
|
|
4. Identify blocked or stuck projects
|
|
5. List incomplete tasks that need attention
|
|
6. Suggest priorities for next week based on patterns
|
|
|
|
### Task Querying
|
|
|
|
When the user asks about tasks:
|
|
- Use Grep to search for task patterns (`- [ ]` for incomplete, `- [x]` for completed)
|
|
- Filter by tags, dates, or folders as requested
|
|
- Present results in organized format
|
|
|
|
## File Patterns
|
|
|
|
- Daily notes: `Daily Journal/YYYY-MM-DD.md`
|
|
- Tasks: Search for `- [ ]` (incomplete) and `- [x]` (completed)
|
|
- Task metadata: `📅 YYYY-MM-DD` for due dates, `#tag` for tags
|
|
|
|
## Template System
|
|
|
|
Daily note template should include:
|
|
- Date header
|
|
- Focus section
|
|
- Tasks query (using Dataview if available)
|
|
- Habit tracking section
|
|
- Notes section
|
|
|
|
## Notes
|
|
|
|
- Always preserve existing file structure and naming conventions
|
|
- Use Obsidian's markdown format with proper frontmatter if needed
|
|
- Respect the Tasks plugin format: `- [ ] Task text 📅 YYYY-MM-DD #tag/context`
|
|
- When creating dates, use ISO format (YYYY-MM-DD)
|