digital-brain
This skill should be used when the user asks to "write a post", "check my voice", "look up contact", "prepare for meeting", "weekly review", "track goals", or mentions personal brand, content creation, network management, or voice consistency.
What this skill does
# Digital Brain A structured personal operating system for managing digital presence, knowledge, relationships, and goals with AI assistance. Designed for founders building in public, content creators growing their audience, and tech-savvy professionals seeking AI-assisted personal management. **Important**: This skill uses progressive disclosure. Module-specific instructions are in each subdirectory's `.md` file. Only load what's needed for the current task. ## When to Activate Activate this skill when the user: - Requests content creation (posts, threads, newsletters) - load identity/voice.md first - Asks for help with personal brand or positioning - Needs to look up or manage contacts/relationships - Wants to capture or develop content ideas - Requests meeting preparation or follow-up - Asks for weekly reviews or goal tracking - Needs to save or retrieve bookmarked resources - Wants to organize research or learning materials **Trigger phrases**: "write a post", "my voice", "content ideas", "who is [name]", "prepare for meeting", "weekly review", "save this", "my goals" ## Core Concepts ### Progressive Disclosure Architecture The Digital Brain follows a three-level loading pattern: | Level | When Loaded | Content | |-------|-------------|---------| | **L1: Metadata** | Always | This SKILL.md overview | | **L2: Module Instructions** | On-demand | `[module]/[MODULE].md` files | | **L3: Data Files** | As-needed | `.jsonl`, `.yaml`, `.md` data | ### File Format Strategy Formats chosen for optimal agent parsing: - **JSONL** (`.jsonl`): Append-only logs - ideas, posts, contacts, interactions - **YAML** (`.yaml`): Structured configs - goals, values, circles - **Markdown** (`.md`): Narrative content - voice, brand, calendar, todos - **XML** (`.xml`): Complex prompts - content generation templates ### Append-Only Data Integrity JSONL files are **append-only**. Never delete entries: - Mark as `"status": "archived"` instead of deleting - Preserves history for pattern analysis - Enables "what worked" retrospectives ## Detailed Topics ### Module Overview ``` digital-brain/ ├── identity/ → Voice, brand, values (READ FIRST for content) ├── content/ → Ideas, drafts, posts, calendar ├── knowledge/ → Bookmarks, research, learning ├── network/ → Contacts, interactions, intros ├── operations/ → Todos, goals, meetings, metrics └── agents/ → Automation scripts ``` ### Identity Module (Critical for Content) **Always read `identity/voice.md` before generating any content.** Contains: - `voice.md` - Tone, style, vocabulary, patterns - `brand.md` - Positioning, audience, content pillars - `values.yaml` - Core beliefs and principles - `bio-variants.md` - Platform-specific bios - `prompts/` - Reusable generation templates ### Content Module Pipeline: `ideas.jsonl` → `drafts/` → `posts.jsonl` - Capture ideas immediately to `ideas.jsonl` - Develop in `drafts/` using `templates/` - Log published content to `posts.jsonl` with metrics - Plan in `calendar.md` ### Network Module Personal CRM with relationship tiers: - `inner` - Weekly touchpoints - `active` - Bi-weekly touchpoints - `network` - Monthly touchpoints - `dormant` - Quarterly reactivation checks ### Operations Module Productivity system with priority levels: - P0: Do today, blocking - P1: This week, important - P2: This month, valuable - P3: Backlog, nice to have ## Practical Guidance ### Content Creation Workflow ``` 1. Read identity/voice.md (REQUIRED) 2. Check identity/brand.md for topic alignment 3. Reference content/posts.jsonl for successful patterns 4. Use content/templates/ as starting structure 5. Draft matching voice attributes 6. Log to posts.jsonl after publishing ``` ### Pre-Meeting Preparation ``` 1. Look up contact: network/contacts.jsonl 2. Get history: network/interactions.jsonl 3. Check pending: operations/todos.md 4. Generate brief with context ``` ### Weekly Review Process ``` 1. Run: python agents/scripts/weekly_review.py 2. Review metrics in operations/metrics.jsonl 3. Check stale contacts: agents/scripts/stale_contacts.py 4. Update goals progress in operations/goals.yaml 5. Plan next week in content/calendar.md ``` ## Examples ### Example: Writing an X Post **Input**: "Help me write a post about AI agents" **Process**: 1. Read `identity/voice.md` → Extract voice attributes 2. Check `identity/brand.md` → Confirm "ai_agents" is a content pillar 3. Reference `content/posts.jsonl` → Find similar successful posts 4. Draft post matching voice patterns 5. Suggest adding to `content/ideas.jsonl` if not publishing immediately **Output**: Post draft in user's authentic voice with platform-appropriate format. ### Example: Contact Lookup **Input**: "Prepare me for my call with Sarah Chen" **Process**: 1. Search `network/contacts.jsonl` for "Sarah Chen" 2. Get recent entries from `network/interactions.jsonl` 3. Check `operations/todos.md` for pending items with Sarah 4. Compile brief: role, context, last discussed, follow-ups **Output**: Pre-meeting brief with relationship context. ## Guidelines 1. **Voice First**: Always read `identity/voice.md` before any content generation 2. **Append Only**: Never delete from JSONL files - archive instead 3. **Update Timestamps**: Set `updated` field when modifying tracked data 4. **Cross-Reference**: Knowledge informs content, network informs operations 5. **Log Interactions**: Always log meetings/calls to `interactions.jsonl` 6. **Preserve History**: Past content in `posts.jsonl` informs future performance ## Integration This skill integrates context engineering principles: - **context-fundamentals** - Progressive disclosure, attention budget management - **memory-systems** - JSONL for persistent memory, structured recall - **tool-design** - Scripts in `agents/scripts/` follow tool design principles - **context-optimization** - Module separation prevents context bloat ## References Internal references: - [Identity Module](./identity/IDENTITY.md) - Voice and brand details - [Content Module](./content/CONTENT.md) - Content pipeline docs - [Network Module](./network/NETWORK.md) - CRM documentation - [Operations Module](./operations/OPERATIONS.md) - Productivity system - [Agent Scripts](./agents/AGENTS.md) - Automation documentation External resources: - [Agent Skills for Context Engineering](https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering) - [Anthropic Context Engineering Guide](https://www.anthropic.com/engineering/effective-context-engineering-for-ai-agents) --- ## Skill Metadata **Created**: 2024-12-29 **Last Updated**: 2024-12-29 **Author**: Murat Can Koylan **Version**: 1.0.0
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".