skills/muratcankoylan__agent-skills-for-context-engineering

mirror of https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering.git synced 2026-09-14 20:36:54 +08:00

Files

T

Muratcan Koylan 9749e5cbda fix: certify production Agent Skills compatibility across Cursor, Claude Code, and Codex (#96 )

* fix: YAML-safe skill frontmatter for cross-platform discovery

Eleven skills used unquoted descriptions containing colons, which strict
YAML parsers reject during skill discovery on Cursor, Claude Code, and
Codex. Normalize all skill frontmatter to valid YAML, add a shared
skill_frontmatter parser with PyYAML validation, fix install docs to use
directory layout, and add .agents/skills symlink plus Open Plugins
skills path declaration.

Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>

* test: add frontmatter parser unit tests and harden examples

Add researcher/scripts/tests/test_skill_frontmatter.py (19 tests) covering
parser edge cases, a strict-YAML regression guard for the unquoted-colon
bug, format/parse round-trips, and corpus + example integration checks.
Wire unit tests into CI ahead of the strict repo gate. Quote the
description fields in the two example skills that had the same
unquoted-colon YAML hazard. Simplify CRLF handling in split_frontmatter
and document CONTRIBUTING test commands.

Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>

* chore: harden production plugin packaging validation

Remove the committed .agents/skills symlink because symlinks are fragile
on Windows checkouts and in plugin packaging. Keep Cursor and Codex
support through Open Plugins discovery and documented directory-copy
manual installs.

Extend validate_repo.py so strict validation checks that the Open
Plugins manifest and Claude marketplace manifest name the same bundled
plugin, and that Open Plugins skills discovery resolves to the same 15
published skills as the repository.

Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>

* ci: certify cross-platform skill compatibility

Add validate_platform_compat.py to check the production surfaces defined by
Agent Skills, Cursor, Claude Code, Codex, and Open Plugins documentation.
The gate validates published skills, manifest discovery parity, and
platform-local directory-copy installs for .cursor/skills, .claude/skills,
.codex/skills, and .agents/skills.

Install skills-ref in CI and require the upstream agentskills reference
validator in the compatibility gate. Tighten manifest path checks so both
Claude marketplace and Open Plugins skill paths must start with './', and
update operator docs to run the new gate before claiming production
readiness.

Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>

---------

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: Muratcan Koylan <muratcankoylan@users.noreply.github.com>

2026-06-29 16:52:07 -04:00

6.9 KiB

Raw Permalink Blame History

name, description, version

name	description	version
digital-brain	This skill should be used for personal operating-system workflows: content creation, voice consistency, relationship lookup, meeting preparation, weekly review, goal tracking, personal brand management, and network management.	1.0.0

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:

Read identity/voice.md → Extract voice attributes
Check identity/brand.md → Confirm "ai_agents" is a content pillar
Reference content/posts.jsonl → Find similar successful posts
Draft post matching voice patterns
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"