Andrew Yim
341d5f5a5b
Custom Skills (ourdigital-custom-skills/): - 00-ourdigital-visual-storytelling: Blog featured image prompt generator - 01-ourdigital-research-publisher: Research-to-publication workflow - 02-notion-organizer: Notion workspace management - 03-research-to-presentation: Notion research to PPT/Figma - 04-seo-gateway-strategist: SEO gateway page strategy planning - 05-gateway-page-content-builder: Gateway page content generation - 20-jamie-brand-editor: Jamie Clinic branded content GENERATION - 21-jamie-brand-guardian: Jamie Clinic content REVIEW & evaluation Refinements applied: - All skills converted to SKILL.md format with YAML frontmatter - Added version fields to all skills - Flattened nested folder structures - Removed packaging artifacts (.zip, .skill files) - Reorganized file structures (scripts/, references/, etc.) - Differentiated Jamie skills with clear roles 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
927 B
927 B
Team Wiki Database
Purpose: Centralized team knowledge and resources.
Schema
| Property | Type | Options | Purpose |
|---|---|---|---|
| Title | title | - | Page name |
| Section | select | Getting Started, Processes, Tools, Reference, Onboarding | Wiki organization |
| Tags | multi_select | - | Topic tags |
| Owner | people | - | Page maintainer |
| Last Updated | last_edited_time | - | Auto-tracked |
| Visibility | select | Public, Team Only, Confidential | Access level |
Usage
Use for team-specific documentation that doesn't fit other databases.
Best Practices
- Organize by sections: Use clear top-level organization
- Assign owners: Every page should have a maintainer
- Control visibility: Set appropriate access levels
- Link extensively: Connect related pages
- Keep current: Regular reviews to remove outdated content