Matty Tiger Skills Plugin
Matty Tiger Skills Plugin
My personal Claude skills plugin for TigerData workflows. Installed in Cowork from the mattstratton/skills-poc GitHub repo.
What it does
The plugin automates my daily workflows: morning briefings (Asana sync, Slack scan, calendar overview), meeting note creation, blog design request automation, weekly content roundups, and LinkedIn article drafts. Every skill loads personal context from this Obsidian vault so Claude knows who I am, my team, and my shorthand.
How it connects to Obsidian
The plugin treats Obsidian as the persistent memory layer. This matters because Cowork starts fresh every session — it has no memory of previous conversations. The plugin solves this by reading from (and occasionally writing to) specific notes in this vault.
Notes the plugin reads
| Note | What for |
|---|---|
00 - System/Claude Context.md |
Memory layer. Loaded at the start of every skill. Contains my role, team, key people, shorthand, active projects, and preferences. This is the "boot file" that makes Claude feel like a colleague instead of a stranger. |
CLAUDE.md (vault root) |
System rules. Folder structure, task formatting (emoji format, Asana link conventions), Dataview patterns, guardrails. Loaded by morning-update. |
03 - Areas/Content Production.md |
Task list. Morning-update syncs Asana tasks into the Upcoming Content section here. |
05 - People/ |
People directory. Meeting-notes resolves calendar attendees against these pages so Dataview linking works. |
04 - Meetings/ |
Meeting notes. Meeting-notes checks for existing notes to avoid duplicates. |
Notes the plugin writes (with approval)
| Note | What for | Which skill |
|---|---|---|
03 - Areas/Content Production.md |
Sync new/changed tasks from Asana | morning-update |
04 - Meetings/YYYY-MM-DD Meeting Name.md |
Create pre-populated meeting notes | meeting-notes |
05 - People/Person Name.md |
Create new People pages for unresolved attendees | meeting-notes |
00 - System/Claude Context.md |
Update the memory layer when things change | context-loader |
All writes require explicit user approval — no skill silently modifies the vault.
Skills
| Skill | Trigger | What it does |
|---|---|---|
/context |
Manual, or auto-loaded by other skills | Loads Claude Context.md so Claude knows who I am. Also handles updates ("add X to my context"). |
/morning-update |
"morning update", "start my day" | Syncs Asana tasks, scans Slack, briefs on calendar and deadlines. Offers to create meeting notes. |
/meeting-notes |
"create meeting notes" | Pulls calendar, resolves attendees to People pages, creates formatted meeting notes. |
/design-requests |
"create design requests", "blog thumbnails" | Searches Content Calendar for blogs, creates design request tasks in Asana. |
/weekly-content |
"/weekly-content Feb 23-27" | Generates weekly content roundup posts for #general and #sales-team. |
/linkedin-articles |
"find me something to share" | Finds articles and drafts LinkedIn posts using Tiger Den voice profile. |
Setup
The plugin is installed via Cowork's plugin system from the GitHub repo. It requires these MCP connectors:
- Obsidian — memory layer, meeting notes, task sync
- Asana — task management, content calendar, design requests
- Slack — message scanning, post delivery
- Google Calendar — schedule, meeting notes
- Tiger Den — marketing references, content library, voice profiles
Maintaining the memory layer
00 - System/Claude Context.md is the persistent memory. When things change (new team member, new project, reporting change, new shorthand), either:
- Tell Claude: "update my context — [change]" and the context-loader skill patches the note
- Edit the note directly in Obsidian
The note should stay concise — it's a hot cache, not an encyclopedia. Detailed info belongs in People pages, Tiger Den references, or project notes. The context note points to those deeper sources.
Repo
Public GitHub: mattstratton/skills-poc. The repo is safe to be public because all confidential context lives in Obsidian (private) or Tiger Den (access-controlled), not in the repo. The repo contains only skill orchestration logic and non-secret config (Asana project IDs, Slack channel names).