Initial commit: Claude Skills Factory with 8 refined custom skills

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>

official-skils-collection/notion-spec-to-implementation/evaluations/basic-spec-implementation.json

@@ -0,0 +1,32 @@
+{
+  "name": "Create Implementation Plan from Spec",
+  "skills": ["spec-to-implementation"],
+  "query": "Create an implementation plan for the User Authentication spec page",
+  "expected_behavior": [
+    "Step 1: Uses Notion:notion-search to find 'User Authentication spec' with keywords like 'User Authentication' or 'auth spec'",
+    "Step 2: If not found or ambiguous, asks user for spec page URL/ID",
+    "Step 3: Fetches spec page using Notion:notion-fetch with URL/ID from search results",
+    "Step 4: Parses spec using patterns from reference/spec-parsing.md to extract requirements, acceptance criteria, constraints",
+    "Step 5: Identifies functional requirements (user stories, features, workflows) and non-functional requirements (performance, security)",
+    "Step 6: Creates implementation plan following structure from reference/templates.md",
+    "Step 7: Includes sections: Overview, Linked Spec, Requirements Summary, Technical Approach, Implementation Phases",
+    "Step 8: Breaks work into logical phases with Goal, Tasks checklist, Estimated effort per phase",
+    "Step 9: Identifies dependencies and risks from spec content",
+    "Step 10: Links plan back to original spec page using <mention-page url='...'>",
+    "Step 11: Creates plan page using Notion:notion-create-pages with appropriate title (e.g., 'Implementation Plan: User Authentication')",
+    "Step 12: Places plan appropriately (asks user or suggests under project/spec parent)"
+  ],
+  "success_criteria": [
+    "Spec is found using Notion:notion-search before attempting to fetch (or user is asked for URL if not found)",
+    "Spec is fetched using Notion:notion-fetch with correct URL/ID from search results",
+    "Plan includes clear overview and spec link with mention-page tag",
+    "Requirements are extracted from actual spec content (not generic) using spec-parsing patterns",
+    "Work is broken into multiple phases (typically 3-5) following template structure",
+    "Each phase has Goal, Tasks (as checkboxes), and Estimated effort",
+    "Dependencies and risks sections are included with specific details from spec",
+    "Plan follows Implementation Plan structure from reference/templates.md",
+    "Success criteria or acceptance criteria from spec are referenced in plan",
+    "Uses correct tool names and sequence: Notion:notion-search → Notion:notion-fetch → Notion:notion-create-pages"
+  ]
+}
+