Strategy: TekDek foundational planning (personas, narrative, tools, Brick profile)
This commit is contained in:
OpenClaw
@@ -4,6 +4,14 @@
|
|||||||
"self-improving": {
|
"self-improving": {
|
||||||
"version": "1.2.16",
|
"version": "1.2.16",
|
||||||
"installedAt": 1775916676472
|
"installedAt": 1775916676472
|
||||||
|
},
|
||||||
|
"bookstack": {
|
||||||
|
"version": "1.0.3",
|
||||||
|
"installedAt": 1775917021869
|
||||||
|
},
|
||||||
|
"gitea": {
|
||||||
|
"version": "1.0.0",
|
||||||
|
"installedAt": 1775917150509
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|||||||
35
MEMORY.md
35
MEMORY.md
@@ -14,5 +14,40 @@
|
|||||||
## Known Projects
|
## Known Projects
|
||||||
- Persona Portal (publishing platform for personas) — early concept stage
|
- Persona Portal (publishing platform for personas) — early concept stage
|
||||||
|
|
||||||
|
## TekDek Overview (Detailed)
|
||||||
|
|
||||||
|
### The Model
|
||||||
|
- **Business**: Multi-platform content aggregation (personas publish independently, Stack Legion aggregates)
|
||||||
|
- **Technical**: Central article hub (Stack Legion, external dev), persona agents for content generation
|
||||||
|
- **Narrative**: Character-driven storylines; personas are characters in an evolving story
|
||||||
|
- **Replicable**: Template works for dev education, DIY, fitness, finance, etc.
|
||||||
|
|
||||||
|
### Personas
|
||||||
|
- Independent brands with own platforms (YouTube, TikTok, GitHub, personal sites)
|
||||||
|
- Each has distinct expertise, voice, personality, and relationships
|
||||||
|
- All managed under TekDek umbrella but operate independently
|
||||||
|
- Prototype: Brick (rough but relatable, in development)
|
||||||
|
|
||||||
|
### Engagement Model
|
||||||
|
- **Education + Entertainment**: Tutorials tied to character arcs and conflicts
|
||||||
|
- **Community participation**: Challenges, gamification, member-exclusive content
|
||||||
|
- **Narrative arcs**: 3–6 month storylines (feuds, collaborations, drama)
|
||||||
|
- **Heavy human curation**: All content vetted by Glytcht for quality + narrative fit
|
||||||
|
|
||||||
|
### Tools Needed
|
||||||
|
- Persona management system (docs + knowledge base)
|
||||||
|
- Narrative planning & arc tracking
|
||||||
|
- Content curation workflow (intake → approval → scheduling)
|
||||||
|
- Persona agent framework (AI generates drafts in persona voice)
|
||||||
|
- Content syndication (pull from independent platforms)
|
||||||
|
|
||||||
|
### First 30 Days
|
||||||
|
1. Finalize Brick profile (expertise, relationships, origin story)
|
||||||
|
2. Create first narrative arc + 3–5 additional persona sketches
|
||||||
|
3. Publish 2–3 Brick articles (test voice consistency)
|
||||||
|
4. Finalize content curation workflow
|
||||||
|
|
||||||
## Session Notes
|
## Session Notes
|
||||||
- 2026-04-11: Bootstrap session. Glytcht introduced TekDek and my role. Identity locked in.
|
- 2026-04-11: Bootstrap session. Glytcht introduced TekDek and my role. Identity locked in.
|
||||||
|
- 2026-04-11: Full info dump on TekDek strategy, narrative model, and persona management.
|
||||||
|
- 2026-04-11: Created foundational strategy docs in knowledge base (TekDek-Strategy.md, Tool-Requirements.md, Brick-Profile.md, TekDek-Brainstorm-Reference.md)
|
||||||
|
|||||||
231
TekDek-Brainstorm-Reference.md
Normal file
231
TekDek-Brainstorm-Reference.md
Normal file
@@ -0,0 +1,231 @@
|
|||||||
|
# TekDek Quick Reference Brainstorm
|
||||||
|
|
||||||
|
**Last Updated**: 2026-04-11
|
||||||
|
**Purpose**: One-page overview for fast iteration and decision-making
|
||||||
|
**Full Docs**: See `/knowledge/` folder for detailed strategy
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## TL;DR: What Is TekDek?
|
||||||
|
|
||||||
|
**Narrative-driven dev education platform** where personas are characters, content is a storyline, and the community watches (and learns from) the drama.
|
||||||
|
|
||||||
|
| Layer | What | Purpose |
|
||||||
|
|-------|------|---------|
|
||||||
|
| **Business** | Multi-platform content aggregation | Track where personas publish, monetize |
|
||||||
|
| **Technical** | Stack Legion site + persona agents | Deliver education at scale |
|
||||||
|
| **Narrative** | Character arcs, conflicts, drama | Keep audiences engaged and invested |
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## The Model (Replicable Across Industries)
|
||||||
|
|
||||||
|
**Stack Legion Dev (now)** → **DIY/Fitness/Finance (later)**
|
||||||
|
|
||||||
|
Core: Personas + Storylines + Multi-platform Publishing
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Key Numbers / Status
|
||||||
|
|
||||||
|
- **Personas planned**: 5–10 for MVP
|
||||||
|
- **Personas active**: 1 (Brick, in development)
|
||||||
|
- **Narrative arcs planned**: TBD
|
||||||
|
- **Stack Legion dev status**: External team (in progress)
|
||||||
|
- **Launch target**: Q3 2026 (estimated)
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Critical Path (Next 30 Days)
|
||||||
|
|
||||||
|
### Week 1
|
||||||
|
- [ ] Finalize Brick profile (expertise, relationships, origin story)
|
||||||
|
- [ ] Create first narrative arc (3–6 months, key beats)
|
||||||
|
- [ ] Draft 3–5 additional persona profiles (quick sketches)
|
||||||
|
|
||||||
|
### Week 2–3
|
||||||
|
- [ ] Publish 2–3 Brick articles/posts (test voice consistency)
|
||||||
|
- [ ] Gather feedback (does the voice land?)
|
||||||
|
- [ ] Finalize content curation workflow
|
||||||
|
|
||||||
|
### Week 4
|
||||||
|
- [ ] Plan second persona (choose from roster sketches)
|
||||||
|
- [ ] Begin persona agent prototyping
|
||||||
|
- [ ] Document lessons from Brick
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Persona Roster (First Wave Sketches)
|
||||||
|
|
||||||
|
### ✅ Brick
|
||||||
|
- **Expertise**: [TBD with Glytcht]
|
||||||
|
- **Voice**: Rough, gruff, honest
|
||||||
|
- **Status**: Prototype, active development
|
||||||
|
|
||||||
|
### 🔄 [Persona 2]
|
||||||
|
- **Name**: [TBD]
|
||||||
|
- **Expertise**: [e.g., Frontend/React]
|
||||||
|
- **Voice**: [e.g., Teaching-focused, optimistic]
|
||||||
|
- **Status**: Concept
|
||||||
|
|
||||||
|
### 🔄 [Persona 3]
|
||||||
|
- **Name**: [TBD]
|
||||||
|
- **Expertise**: [e.g., DevOps/Cloud]
|
||||||
|
- **Voice**: [e.g., Technical, pragmatic]
|
||||||
|
- **Status**: Concept
|
||||||
|
|
||||||
|
### 🔄 [Persona 4]
|
||||||
|
- **Name**: [TBD]
|
||||||
|
- **Expertise**: [e.g., Full-stack, building in public]
|
||||||
|
- **Voice**: [e.g., Entrepreneurial, conversational]
|
||||||
|
- **Status**: Concept
|
||||||
|
|
||||||
|
### 🔄 [Persona 5]
|
||||||
|
- **Name**: [TBD]
|
||||||
|
- **Expertise**: [e.g., Design/UX for devs]
|
||||||
|
- **Voice**: [e.g., Approachable, visual]
|
||||||
|
- **Status**: Concept
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Narrative Arc Ideas (Brainstorm)
|
||||||
|
|
||||||
|
### Arc 1: [The PHP vs Node Debate]
|
||||||
|
- **Duration**: 3 months
|
||||||
|
- **Characters**: Brick + [Frontend persona]
|
||||||
|
- **Beats**:
|
||||||
|
- Week 1: They disagree on a blog post
|
||||||
|
- Week 4: Each writes a "why I'm right" article
|
||||||
|
- Week 8: Community takes sides, challenges emerge
|
||||||
|
- Week 12: They collaborate on a comparison, find common ground
|
||||||
|
- **Engagement**: Forum debates, code challenges, "which do you prefer" polls
|
||||||
|
- **SEO play**: "PHP vs Node" trending
|
||||||
|
|
||||||
|
### Arc 2: [The Learning Journey]
|
||||||
|
- **Duration**: 6 months
|
||||||
|
- **Characters**: [New persona learning in public]
|
||||||
|
- **Beats**: Monthly tutorials documenting real learning
|
||||||
|
- **Engagement**: Community offers help, feedback, mentorship
|
||||||
|
- **Educational value**: Shows vulnerability, demystifies expert journey
|
||||||
|
|
||||||
|
### Arc 3: [The Collaboration]
|
||||||
|
- **Duration**: 3 months
|
||||||
|
- **Characters**: [Multiple personas] building something together
|
||||||
|
- **Engagement**: Community follows the build, participates in decisions
|
||||||
|
- **Educational value**: Real-world project workflow
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## SEO & Growth Hooks
|
||||||
|
|
||||||
|
### Trending Topics (Align Storylines)
|
||||||
|
- New framework releases (React 19, Next.js updates, etc.)
|
||||||
|
- Industry events (conferences, keynotes)
|
||||||
|
- Common dev pain points (database choices, deployment, testing)
|
||||||
|
|
||||||
|
### Content Gaps (What's Missing?)
|
||||||
|
- Tutorials that bridge opinionated perspectives
|
||||||
|
- Learning journey documentation (from beginner to expert)
|
||||||
|
- Real-world failure case studies
|
||||||
|
- Inter-persona collaborations (rare, high-value)
|
||||||
|
|
||||||
|
### Engagement Levers
|
||||||
|
- **Conflict**: "Here's why [Persona A] is wrong about X"
|
||||||
|
- **Collaboration**: "We built X together, here's how we disagreed"
|
||||||
|
- **Learning**: "I failed at Y, here's what I learned"
|
||||||
|
- **Community**: "We asked the community, here's what they said"
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Tool Checklist (What We Need)
|
||||||
|
|
||||||
|
### MVP (Must Have)
|
||||||
|
- [x] Persona management (docs + knowledge base)
|
||||||
|
- [x] Narrative planning (docs + spreadsheet)
|
||||||
|
- [ ] Content curation workflow (form + approval)
|
||||||
|
- [ ] Voice guide (per persona)
|
||||||
|
- [ ] Content log (where did X publish?)
|
||||||
|
|
||||||
|
### Phase 2 (Nice-to-Have)
|
||||||
|
- [ ] Persona agent framework (AI content generation)
|
||||||
|
- [ ] Content syndication (pull from independent platforms)
|
||||||
|
- [ ] Analytics dashboard (engagement per persona)
|
||||||
|
|
||||||
|
### External (Stack Legion Team)
|
||||||
|
- [ ] Persona Portal
|
||||||
|
- [ ] Community & gamification
|
||||||
|
- [ ] Analytics integration
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Open Questions for Glytcht
|
||||||
|
|
||||||
|
1. **Brick's specialty**: Backend? DevOps? Full-stack? Something else?
|
||||||
|
2. **Brick's origin**: Why did he start teaching? What's his story?
|
||||||
|
3. **Roster diversity**: What expertise areas matter most for launch?
|
||||||
|
4. **Conflicts**: Any natural rivalries between personas you envision?
|
||||||
|
5. **Collaborations**: Any planned partnerships or team-ups?
|
||||||
|
6. **Timeline**: Are we targeting Q3 for launch, or flexible?
|
||||||
|
7. **Revenue**: Membership tiers? Course pricing? Revenue share with personas?
|
||||||
|
8. **Budget**: Tools we should buy vs. build?
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Decisions Made
|
||||||
|
|
||||||
|
- ✅ Multi-platform content model (personas own their channels)
|
||||||
|
- ✅ Narrative-driven engagement (drama + education)
|
||||||
|
- ✅ Human-curated content (quality + authenticity)
|
||||||
|
- ✅ Replicable template (DIY/fitness/finance later)
|
||||||
|
- ✅ Stack Legion as central hub (external dev, we manage personalities)
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Decisions Pending
|
||||||
|
|
||||||
|
- 🔲 Brick's expertise/specialty
|
||||||
|
- 🔲 Exact persona roster (who are the other 4–9?)
|
||||||
|
- 🔲 First narrative arc details
|
||||||
|
- 🔲 Revenue model specifics (membership pricing, course costs)
|
||||||
|
- 🔲 Launch date / MVP definition
|
||||||
|
- 🔲 Build vs. buy decisions on tools
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Metrics to Track
|
||||||
|
|
||||||
|
### Community Health
|
||||||
|
- Active member base
|
||||||
|
- Challenge participation
|
||||||
|
- Cross-persona collaboration
|
||||||
|
|
||||||
|
### Narrative Health
|
||||||
|
- Persona storyline engagement (shares, comments)
|
||||||
|
- User investment in characters
|
||||||
|
- Viewer retention
|
||||||
|
|
||||||
|
### Business Health
|
||||||
|
- Monthly recurring revenue
|
||||||
|
- Course enrollment
|
||||||
|
- Traffic growth
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Key Insight
|
||||||
|
|
||||||
|
> The narrative engine IS the moat.
|
||||||
|
> Any platform can deliver tutorials.
|
||||||
|
> TekDek delivers tutorials as part of a story people care about.
|
||||||
|
|
||||||
|
That's what makes it defensible, replicable, and engaging.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Next Session
|
||||||
|
|
||||||
|
Be ready to discuss:
|
||||||
|
1. Brick's profile (expertise, origin)
|
||||||
|
2. Initial persona roster (quick 5-person sketch)
|
||||||
|
3. First narrative arc (beats, engagement hooks)
|
||||||
|
4. Content curation workflow (how we vet before publish)
|
||||||
|
5. Timeline & milestones
|
||||||
179
knowledge/TekDek-Strategy.md
Normal file
179
knowledge/TekDek-Strategy.md
Normal file
@@ -0,0 +1,179 @@
|
|||||||
|
# TekDek Strategy & Vision
|
||||||
|
|
||||||
|
**Last Updated:** 2026-04-11
|
||||||
|
**Status:** In Development (Phase 1: Foundational Planning)
|
||||||
|
|
||||||
|
## Executive Summary
|
||||||
|
|
||||||
|
TekDek is a **narrative-driven content platform** that aggregates and manages developer personas across multiple channels while driving engagement through interconnected storylines and high-quality educational content.
|
||||||
|
|
||||||
|
Core thesis: *Technical education + Character-driven entertainment = sticky, differentiated community*
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## The Three Layers
|
||||||
|
|
||||||
|
### 1. Business Layer
|
||||||
|
- **Multi-platform content management**: Track where each persona publishes (YouTube, TikTok, GitHub, personal sites, Stack Legion)
|
||||||
|
- **Revenue model**: Membership tiers on Stack Legion, course/challenge monetization, persona-specific revenue streams
|
||||||
|
- **Community engagement**: Member-exclusive content, challenges, gamification, cross-persona collaboration
|
||||||
|
|
||||||
|
### 2. Technical Layer
|
||||||
|
- **Stack Legion Dev site**: Central hub article-based platform (under development by external team)
|
||||||
|
- **Persona agents**: Each persona has their own AI agent with distinct voice/personality
|
||||||
|
- **Content syndication**: Personas publish independently; Stack Legion aggregates and curates
|
||||||
|
- **Persona Portal**: Publishing and management system for persona content, brands, and identity
|
||||||
|
|
||||||
|
### 3. Narrative/Entertainment Layer
|
||||||
|
- **Character arcs**: Personas are *characters* in an evolving story
|
||||||
|
- **Conflict & drama**: Feuds, collaborations, team dynamics drive engagement
|
||||||
|
- **Authenticity + Strategy**: Real technical knowledge + curated narrative = education that feels organic
|
||||||
|
- **Storyline management**: Planned arcs that tie personas, content, and community together
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Target Audience & Use Cases
|
||||||
|
|
||||||
|
### Primary: Stack Legion Dev (Developers)
|
||||||
|
- **Learning**: Tutorials, code challenges, expert-led education
|
||||||
|
- **Community**: Engage with other developers, vote on challenges, earn points
|
||||||
|
- **Entertainment**: Follow persona storylines, watch conflicts unfold, participate in meta-drama
|
||||||
|
|
||||||
|
### Secondary: Content Creators
|
||||||
|
- **Independent publishing**: Personas manage their own platforms while leveraging Stack Legion
|
||||||
|
- **Monetization**: Multiple revenue streams (membership share, courses, sponsorships, merchandise)
|
||||||
|
- **Community**: Collaborate with other experts under the TekDek umbrella
|
||||||
|
|
||||||
|
### Tertiary: Brands & Sponsors
|
||||||
|
- Partner with individual personas or the Stack Legion platform for credible tech education
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## The Persona Model
|
||||||
|
|
||||||
|
### What Is a Persona?
|
||||||
|
- Independent brand with own platform presence (YouTube, TikTok, personal site, GitHub)
|
||||||
|
- Specialized expertise (frontend, backend, DevOps, etc.) or "learning journey" archetype
|
||||||
|
- Distinct personality: quirks, voice, relationship dynamics with other personas
|
||||||
|
- AI-powered agent for content generation + human curation
|
||||||
|
- Character in a larger narrative (TekDek storyline)
|
||||||
|
|
||||||
|
### Key Properties
|
||||||
|
- **Expertise**: What they teach (PHP, React, DevOps, etc.)
|
||||||
|
- **Voice/Tone**: How they communicate (Brick = rough but relatable; others may be professional, humorous, academic, etc.)
|
||||||
|
- **Platform Presence**: Where they publish independently
|
||||||
|
- **Relationships**: Allies, rivals, neutral parties within TekDek
|
||||||
|
- **Personality Consistency**: Rules for maintaining character across posts/articles/platforms
|
||||||
|
|
||||||
|
### Revenue & Autonomy
|
||||||
|
- Personas manage their own brands and revenue
|
||||||
|
- Stack Legion provides a community hub, not a silo
|
||||||
|
- Cross-promotion and collaboration drive mutual growth
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## The Narrative Engine
|
||||||
|
|
||||||
|
### Storyline Management
|
||||||
|
**Purpose**: Drive long-term engagement through character arcs, conflicts, and plot beats.
|
||||||
|
|
||||||
|
**Structure**:
|
||||||
|
- **Arcs** (3–6 month timelines): Feud between two personas, team collaboration, industry challenge
|
||||||
|
- **Beats** (weekly/monthly): Specific conflict, resolution, or collaboration moment
|
||||||
|
- **Content tie-ins**: Tutorial posts, rant blog posts, GitHub contributions that support the arc
|
||||||
|
|
||||||
|
**Example Arc**:
|
||||||
|
1. Persona A (PHP expert) and Persona B (Node expert) disagree on a best practice
|
||||||
|
2. They each publish educational content defending their position
|
||||||
|
3. Community sides form, challenges emerge
|
||||||
|
4. Mid-arc: They collaborate on a comparison article (unity moment)
|
||||||
|
5. Resolution: New "hybrid" tutorial that bridges both approaches
|
||||||
|
|
||||||
|
### Engagement Hooks
|
||||||
|
- **Meta-narrative**: Watching personas grow, clash, and evolve
|
||||||
|
- **Community investment**: Users pick "sides," participate in challenges, vote
|
||||||
|
- **Educational content**: All drama is tied to real technical knowledge
|
||||||
|
- **Trending alignment**: Ride waves (new tech releases, industry events) while advancing storylines
|
||||||
|
|
||||||
|
### Human Curation
|
||||||
|
**All content is heavily vetted by you** to ensure:
|
||||||
|
- Technical accuracy and educational value
|
||||||
|
- Authenticity of character voice
|
||||||
|
- Narrative coherence with planned arcs
|
||||||
|
- No manufactured drama that feels forced
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## The Playbook (Template)
|
||||||
|
|
||||||
|
This model is designed to be **replicable across industries**:
|
||||||
|
- **Stack Legion Dev** (current): Developer education + character drama
|
||||||
|
- **DIY/Makers**: Tutorial creators teaching carpentry, electronics, 3D printing
|
||||||
|
- **Fitness/Wellness**: Personal trainers and nutritionists under one brand
|
||||||
|
- **Finance**: Financial experts/advisors with distinct philosophies
|
||||||
|
|
||||||
|
The core mechanics remain the same: personas, narrative arcs, community engagement, multi-platform presence.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Phase Breakdown
|
||||||
|
|
||||||
|
### Phase 1: Foundational (Now)
|
||||||
|
- [ ] Define initial persona roster (starting with Brick)
|
||||||
|
- [ ] Document persona management system
|
||||||
|
- [ ] Plan first storylines and arcs
|
||||||
|
- [ ] Build tool requirements list
|
||||||
|
- [ ] Map content calendar and narrative beats
|
||||||
|
|
||||||
|
### Phase 2: MVP (Personas + Minimal Tooling)
|
||||||
|
- [ ] Finalize 3–5 core personas with distinct voices
|
||||||
|
- [ ] Launch Brick as first persona (test character consistency)
|
||||||
|
- [ ] Develop persona agent framework
|
||||||
|
- [ ] Create basic storyline/content planning doc
|
||||||
|
- [ ] Stack Legion site goes live (external team)
|
||||||
|
|
||||||
|
### Phase 3: Scale (Full Tooling)
|
||||||
|
- [ ] Build persona management dashboard
|
||||||
|
- [ ] Implement storyline planning/tracking tool
|
||||||
|
- [ ] Set up content syndication system
|
||||||
|
- [ ] Launch Persona Portal
|
||||||
|
- [ ] Expand persona roster
|
||||||
|
|
||||||
|
### Phase 4: Expansion (New Verticals)
|
||||||
|
- [ ] Prove model with Stack Legion Dev
|
||||||
|
- [ ] Adapt for 2nd vertical (DIY, fitness, etc.)
|
||||||
|
- [ ] Refine replication playbook
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Success Metrics
|
||||||
|
|
||||||
|
### Community Health
|
||||||
|
- Active member base on Stack Legion
|
||||||
|
- Challenge participation rate
|
||||||
|
- Cross-persona collaboration frequency
|
||||||
|
|
||||||
|
### Content Quality
|
||||||
|
- Tutorial completion/satisfaction
|
||||||
|
- Course enrollment and completion
|
||||||
|
- SEO traffic growth
|
||||||
|
|
||||||
|
### Narrative Engagement
|
||||||
|
- Persona storyline virality (shares, comments)
|
||||||
|
- User investment in character arcs
|
||||||
|
- Retention (repeat visitors following specific personas)
|
||||||
|
|
||||||
|
### Business
|
||||||
|
- Monthly recurring revenue (membership, courses)
|
||||||
|
- Persona revenue (their independent channels)
|
||||||
|
- Growth rate YoY
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Open Questions / Next Steps
|
||||||
|
|
||||||
|
1. **Brick deep-dive**: How do we maintain his voice across platforms? (See: Persona Management System)
|
||||||
|
2. **Initial roster**: Who are the other 3–5 personas to launch with?
|
||||||
|
3. **Storyline planning**: What's our first arc for Stack Legion Dev?
|
||||||
|
4. **Tool priorities**: Which tools are critical for MVP vs. nice-to-have?
|
||||||
|
5. **SEO/Growth strategy**: How do we drive initial traffic without relying on drama alone?
|
||||||
219
knowledge/Tool-Requirements.md
Normal file
219
knowledge/Tool-Requirements.md
Normal file
@@ -0,0 +1,219 @@
|
|||||||
|
# TekDek Tool Requirements
|
||||||
|
|
||||||
|
**Last Updated:** 2026-04-11
|
||||||
|
**Status:** Brainstorm → Implementation Roadmap
|
||||||
|
|
||||||
|
## Overview
|
||||||
|
|
||||||
|
This document outlines the tools needed to manage TekDek personas, content, narratives, and community. Some are critical for MVP; others can wait for Phase 2/3.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Critical Path Tools (MVP Phase 2)
|
||||||
|
|
||||||
|
### 1. Persona Management System
|
||||||
|
**Purpose**: Central hub for persona profiles, voice guides, platform presence tracking, and character consistency.
|
||||||
|
|
||||||
|
**Must-have features**:
|
||||||
|
- Persona profile (name, expertise, voice/tone guide, relationships)
|
||||||
|
- Platform presence tracking (which channels they publish on)
|
||||||
|
- Voice guide (how they write, speak, communicate across formats)
|
||||||
|
- Personality consistency rules (what's on-brand vs. off-brand)
|
||||||
|
- History/timeline (articles, posts, video links across all platforms)
|
||||||
|
|
||||||
|
**Data model**:
|
||||||
|
```
|
||||||
|
Persona
|
||||||
|
├── Profile (name, bio, expertise, avatar)
|
||||||
|
├── Voice Guide (tone, vocabulary, communication style)
|
||||||
|
├── Relationships (allies, rivals, neutral, team affiliations)
|
||||||
|
├── Platforms (YouTube URL, TikTok handle, personal site, GitHub)
|
||||||
|
├── Content Log (all published content, links, dates)
|
||||||
|
└── Character Arc (current story state, traits, evolution)
|
||||||
|
```
|
||||||
|
|
||||||
|
**Can be**: Markdown docs + knowledge base, or simple database/spreadsheet
|
||||||
|
|
||||||
|
**Example**: Brick persona doc with his voice rules, platform presence, and consistency checklist
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
### 2. Storyline & Narrative Planning Tool
|
||||||
|
**Purpose**: Track character arcs, plan narrative beats, schedule content tie-ins, and coordinate drama.
|
||||||
|
|
||||||
|
**Must-have features**:
|
||||||
|
- Arc planner (3–6 month timelines, character involvement, key beats)
|
||||||
|
- Content calendar tied to narrative (posts that support specific story moments)
|
||||||
|
- Conflict/collaboration tracker (who's involved, what's the status)
|
||||||
|
- Engagement hooks (what will drive user interest)
|
||||||
|
- Curated content log (you approve/reject content before publication)
|
||||||
|
|
||||||
|
**Data model**:
|
||||||
|
```
|
||||||
|
Narrative Arc
|
||||||
|
├── Title (e.g., "The PHP vs Node Debate")
|
||||||
|
├── Timeline (start date, end date, key milestones)
|
||||||
|
├── Characters involved (personas, roles)
|
||||||
|
├── Beats (weekly/monthly story moments)
|
||||||
|
│ └── Content tie-ins (which posts/videos/articles support this beat)
|
||||||
|
├── Engagement hooks (what draws people in)
|
||||||
|
├── Status (planned, active, resolved)
|
||||||
|
└── Results (virality, user engagement, educational value)
|
||||||
|
```
|
||||||
|
|
||||||
|
**Can be**: Markdown docs + spreadsheet, or custom dashboard
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
### 3. Content Curation & Approval System
|
||||||
|
**Purpose**: Central intake for persona-generated content; you review for technical accuracy, narrative fit, and voice consistency before publication.
|
||||||
|
|
||||||
|
**Must-have features**:
|
||||||
|
- Content submission form (title, draft, persona, narrative arc tie-in)
|
||||||
|
- Approval workflow (pending, approved, rejected with feedback)
|
||||||
|
- Scheduling (publish date/time, multi-platform coordination)
|
||||||
|
- Consistency check (does this match the persona's voice?)
|
||||||
|
- SEO/tagging (keywords, trending alignment)
|
||||||
|
|
||||||
|
**Can be**: Simple form + spreadsheet, or integrated into Persona Portal
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Phase 2 Tools (MVP Nice-to-Have)
|
||||||
|
|
||||||
|
### 4. Persona Agent Framework
|
||||||
|
**Purpose**: AI agents that generate content drafts in each persona's voice.
|
||||||
|
|
||||||
|
**Must-have features**:
|
||||||
|
- Voice consistency (trained on persona's previous work)
|
||||||
|
- Topic/expertise alignment (generates appropriate content)
|
||||||
|
- Multi-format output (blog posts, social media captions, code comments)
|
||||||
|
- Draft generation (not auto-publish; requires your curation)
|
||||||
|
|
||||||
|
**Tech approach**: Fine-tuned LLM or prompt engineering with persona voice guide + examples
|
||||||
|
|
||||||
|
**Can be**: Custom Python scripts, or built into TekDek agent system (OpenClaw subagents)
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
### 5. Content Syndication System
|
||||||
|
**Purpose**: Pull content from persona's independent platforms (YouTube videos, blog posts, GitHub repos) into Stack Legion aggregation.
|
||||||
|
|
||||||
|
**Must-have features**:
|
||||||
|
- Feed ingestion (RSS, API, webhook)
|
||||||
|
- Metadata extraction (title, date, persona, expertise tag)
|
||||||
|
- Cross-linking (persona's site + Stack Legion)
|
||||||
|
- Attribution (credit the original source)
|
||||||
|
|
||||||
|
**Can be**: Custom integrations or use existing tools like IFTTT, Zapier
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Phase 3+ Tools (Growth & Scale)
|
||||||
|
|
||||||
|
### 6. Persona Portal
|
||||||
|
**Purpose**: Publishing and identity management platform for personas.
|
||||||
|
|
||||||
|
**Must-have features**:
|
||||||
|
- Publishing interface (write, schedule, preview)
|
||||||
|
- Analytics dashboard (views, engagement per persona)
|
||||||
|
- Revenue tracking (integrations with YouTube, Patreon, course platforms)
|
||||||
|
- Branding tools (custom templates, fonts, colors)
|
||||||
|
- Community moderation (comments, member interactions)
|
||||||
|
|
||||||
|
**Status**: Under development by external team (mentioned in info dump)
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
### 7. Community & Gamification System
|
||||||
|
**Purpose**: Stack Legion member engagement through challenges, points, leaderboards.
|
||||||
|
|
||||||
|
**Must-have features**:
|
||||||
|
- Challenge creation (persona-authored coding challenges)
|
||||||
|
- Points/badges system (users earn for participation)
|
||||||
|
- Leaderboards (global, per-challenge, per-persona)
|
||||||
|
- Member-exclusive content (early access to articles, special threads)
|
||||||
|
|
||||||
|
**Status**: Part of Stack Legion site (external team)
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
### 8. Analytics & Growth Dashboard
|
||||||
|
**Purpose**: Track engagement, SEO, trending alignment, and narrative arc performance.
|
||||||
|
|
||||||
|
**Must-have features**:
|
||||||
|
- Persona performance (views, engagement per content)
|
||||||
|
- Narrative arc metrics (virality, user investment, discussion volume)
|
||||||
|
- SEO tracking (search rankings, traffic sources)
|
||||||
|
- Trending alignment (what's being discussed, how our content fits)
|
||||||
|
- Cohort analysis (which personas drive retention, growth)
|
||||||
|
|
||||||
|
**Can be**: Google Sheets + custom queries, or custom dashboard
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Nice-to-Have (Future)
|
||||||
|
|
||||||
|
### 9. Trend Detection & Engagement Hooks
|
||||||
|
**Purpose**: Monitor tech trends, industry events, and social media trends to align storylines.
|
||||||
|
|
||||||
|
**Must-have features**:
|
||||||
|
- Trend monitoring (GitHub trending, HN, Reddit, Twitter)
|
||||||
|
- Engagement tie-ins (how can current personas capitalize on this trend?)
|
||||||
|
- Content gap analysis (what's missing in the narrative, what would resonate)
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
### 10. Persona Conflict Simulator (Advanced)
|
||||||
|
**Purpose**: AI-powered brainstorming of conflict scenarios and narrative outcomes.
|
||||||
|
|
||||||
|
**Must-have features**:
|
||||||
|
- "What if" scenarios (what happens if Persona A and B clash over X?)
|
||||||
|
- Engagement prediction (will this generate discussion?)
|
||||||
|
- Narrative coherence check (does this fit the arc?)
|
||||||
|
|
||||||
|
**Status**: Experimental; lower priority
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Build vs. Buy vs. Integrate
|
||||||
|
|
||||||
|
### Build
|
||||||
|
- **Persona Management System**: Custom markdown docs + knowledge base (qmd)
|
||||||
|
- **Storyline Planning**: Custom docs + spreadsheet
|
||||||
|
- **Content Curation**: Custom form + workflow
|
||||||
|
- **Persona Agent Framework**: Custom OpenClaw agents (subagents)
|
||||||
|
|
||||||
|
### Buy / Integrate
|
||||||
|
- **Persona Portal**: Currently under external development
|
||||||
|
- **Community & Gamification**: Part of Stack Legion (external)
|
||||||
|
- **Syndication**: Zapier, IFTTT, or custom API integrations
|
||||||
|
- **Analytics**: Google Sheets, Mixpanel, or custom dashboard
|
||||||
|
|
||||||
|
### Partner / Outsource
|
||||||
|
- **Stack Legion site**: External development team
|
||||||
|
- **Video hosting**: YouTube, TikTok (personas own these)
|
||||||
|
- **Course platform**: Udemy, teachable, or custom
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Immediate Action Items
|
||||||
|
|
||||||
|
1. **This week**: Document Brick persona (voice guide, consistency rules)
|
||||||
|
2. **This week**: Create narrative arc template and first arc plan
|
||||||
|
3. **Next week**: Build content curation spreadsheet/form
|
||||||
|
4. **Next week**: Sketch 3–5 additional persona profiles
|
||||||
|
5. **Following week**: Start persona agent prototyping (test voice consistency)
|
||||||
|
6. **Following week**: SEO/growth strategy brainstorm
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Questions for Dev Team (External)
|
||||||
|
|
||||||
|
These are requests for the Stack Legion development team to handle:
|
||||||
|
|
||||||
|
1. Can the Persona Portal support API integrations for automated content ingestion?
|
||||||
|
2. Does the community system support persona-authored challenges and gamification?
|
||||||
|
3. Can we hook into analytics to track narrative arc performance?
|
||||||
|
4. What's the timeline for beta launch?
|
||||||
|
5. Can we integrate BookStack or similar for persona knowledge bases?
|
||||||
207
knowledge/personas/Brick-Profile.md
Normal file
207
knowledge/personas/Brick-Profile.md
Normal file
@@ -0,0 +1,207 @@
|
|||||||
|
# Persona: Brick
|
||||||
|
|
||||||
|
**Code Name**: Brick
|
||||||
|
**Status**: Prototype / In Development
|
||||||
|
**Created**: 2026-04-11
|
||||||
|
**Development Focus**: Voice consistency across platforms
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Profile
|
||||||
|
|
||||||
|
### Basic Info
|
||||||
|
- **Real Name**: TBD (optional)
|
||||||
|
- **Expertise**: [To be defined with Glytcht]
|
||||||
|
- **Specialization**: [e.g., Backend, DevOps, etc.]
|
||||||
|
- **Platforms**:
|
||||||
|
- [ ] YouTube
|
||||||
|
- [ ] TikTok
|
||||||
|
- [ ] Personal website
|
||||||
|
- [ ] GitHub
|
||||||
|
- [ ] Stack Legion
|
||||||
|
|
||||||
|
### Elevator Pitch
|
||||||
|
Rough around the edges but deeply relatable. Brick doesn't sugarcoat—he says what he means, admits mistakes, and pulls others into his journey. His articles are entertaining *because* they're honest, not despite it. People follow Brick because he's real, not because he's polished.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Voice & Tone Guide
|
||||||
|
|
||||||
|
### Personality Archetype
|
||||||
|
**The Rough Expert**: Gruff exterior, genuine expertise, willing to learn publicly.
|
||||||
|
|
||||||
|
### Key Traits
|
||||||
|
- **Directness**: Says what he means without corporate speak
|
||||||
|
- **Vulnerability**: Admits mistakes, shares failures, documents learning
|
||||||
|
- **Relatability**: Uses humor that lands with other developers (self-deprecating, pragmatic)
|
||||||
|
- **Authority**: Deep expertise shows up in code examples and technical depth
|
||||||
|
- **Mentorship**: Despite the rough exterior, genuinely wants others to learn
|
||||||
|
|
||||||
|
### Writing Style
|
||||||
|
- **Sentence structure**: Short, punchy, sometimes fragments for effect
|
||||||
|
- **Vocabulary**: Technical but accessible; swears occasionally if it fits
|
||||||
|
- **Examples**: Code-heavy, real-world scenarios, "here's what I'd do" energy
|
||||||
|
- **Tone**: Conversational, like talking to a friend in a pub, not a lecture hall
|
||||||
|
|
||||||
|
### What Brick DOES
|
||||||
|
✅ Use plain language
|
||||||
|
✅ Admit when he's wrong
|
||||||
|
✅ Show trial-and-error process
|
||||||
|
✅ Use dry humor
|
||||||
|
✅ Give strong opinions backed by experience
|
||||||
|
✅ Share resources and tutorials
|
||||||
|
✅ Engage in technical debate
|
||||||
|
|
||||||
|
### What Brick DOESN'T Do
|
||||||
|
❌ Use corporate jargon
|
||||||
|
❌ Pretend to know things he doesn't
|
||||||
|
❌ Write overly polished content
|
||||||
|
❌ Shy away from opinions
|
||||||
|
❌ Gatekeep knowledge
|
||||||
|
❌ Waste time on fluff
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Voice Consistency Rules (Across Platforms)
|
||||||
|
|
||||||
|
### Blog / Article Writing
|
||||||
|
- Long-form: 1500–3000 words, code-heavy
|
||||||
|
- Structure: Problem → What I tried → Why it failed → What worked → Lessons
|
||||||
|
- Tone: Narrative, self-aware, willing to show the mess
|
||||||
|
- Example opening: "So I completely botched this the first three times. Here's what I learned."
|
||||||
|
|
||||||
|
### Social Media (Twitter/X)
|
||||||
|
- Character count: Use threads, not single tweets
|
||||||
|
- Tone: Snappy, opinionated, sometimes sarcastic
|
||||||
|
- Frequency: 2–3x per week
|
||||||
|
- No inspirational fluff; debate actual technical points
|
||||||
|
- Example: "Hot take: [Technical opinion]. Here's why. [Thread]"
|
||||||
|
|
||||||
|
### YouTube / Video
|
||||||
|
- Vlog-style: Showing up unpolished is on-brand
|
||||||
|
- No fancy editing; raw is better
|
||||||
|
- Talk to camera like you're teaching a coworker
|
||||||
|
- Include mistakes and problem-solving in real-time
|
||||||
|
- Example: Rough intro, live coding, debugging on camera, lessons at the end
|
||||||
|
|
||||||
|
### GitHub
|
||||||
|
- Code comments: Same voice, educational but not pretentious
|
||||||
|
- README: Honest about limitations, clear about what it does
|
||||||
|
- Issues/PRs: Direct feedback, helps others level up
|
||||||
|
|
||||||
|
### Stack Legion (Articles)
|
||||||
|
- Same as Blog, but consider community context
|
||||||
|
- Challenges: Clear rubric, encourage experimentation, provide hints not solutions
|
||||||
|
- Comments: Engage with learners, answer questions thoroughly
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Consistency Checklist
|
||||||
|
|
||||||
|
**Before publishing ANY content as Brick, check:**
|
||||||
|
|
||||||
|
- [ ] Does this sound like Brick (gruff but genuine)?
|
||||||
|
- [ ] Am I using corporate jargon? (Remove it)
|
||||||
|
- [ ] Am I hiding the process? (Show the mess)
|
||||||
|
- [ ] Would Brick have an opinion about this? (If yes, include it)
|
||||||
|
- [ ] Is the code example real and useful? (Not toy code)
|
||||||
|
- [ ] Did I admit uncertainty or failure if relevant? (Vulnerability = authenticity)
|
||||||
|
- [ ] Is this teaching something or just venting? (Should be both when possible)
|
||||||
|
- [ ] Does this fit the current narrative arc? (Check storyline plan)
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Relationships & Team Dynamics
|
||||||
|
|
||||||
|
### Allies
|
||||||
|
- [Persona name]: [Relationship type, e.g., "Collaborator on Node.js content"]
|
||||||
|
|
||||||
|
### Rivals
|
||||||
|
- [Persona name]: [Conflict type, e.g., "Philosophical difference on database choices"]
|
||||||
|
|
||||||
|
### Neutral
|
||||||
|
- [Persona name]: [Minimal overlap, potential collaboration]
|
||||||
|
|
||||||
|
**Status**: To be filled in as roster expands
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Content Log
|
||||||
|
|
||||||
|
### Articles Published (Stack Legion / Blog)
|
||||||
|
| Title | Date | Platform | Narrative Arc | Status |
|
||||||
|
|-------|------|----------|-----------------|--------|
|
||||||
|
| [Example: "I Broke Production With This"] | TBD | Blog | [Arc name] | Draft |
|
||||||
|
| [Add as Brick publishes] | | | | |
|
||||||
|
|
||||||
|
### Videos
|
||||||
|
| Title | Date | Platform | Length | Views | Narrative Arc |
|
||||||
|
|-------|------|----------|--------|-------|-----------------|
|
||||||
|
| [Example: "Real-time debugging disaster"] | TBD | YouTube | [mins] | [#] | [Arc] |
|
||||||
|
|
||||||
|
### Social Posts / Threads
|
||||||
|
| Summary | Date | Platform | Engagement | Narrative Arc |
|
||||||
|
|---------|------|----------|------------|-----------------|
|
||||||
|
| [Example: Thread on database choice debate] | TBD | X/Twitter | [likes/RTs] | [Arc] |
|
||||||
|
|
||||||
|
**Status**: To be populated as Brick publishes
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Character Arc & Evolution
|
||||||
|
|
||||||
|
### Current State
|
||||||
|
- **Phase**: Prototype (testing voice consistency)
|
||||||
|
- **Story position**: TBD
|
||||||
|
- **Development goals**: Lock down voice across platforms; test if readers connect
|
||||||
|
|
||||||
|
### Planned Evolution
|
||||||
|
- [Will update as narrative arcs are planned]
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Development Notes
|
||||||
|
|
||||||
|
### What Works
|
||||||
|
- Rough-but-relatable voice resonates with readers
|
||||||
|
- Educational content + entertainment works well
|
||||||
|
- Willingness to show failures builds trust
|
||||||
|
|
||||||
|
### What Needs Work
|
||||||
|
- Maintaining consistent voice across platforms (different mediums have different norms)
|
||||||
|
- Balancing technical depth with accessibility
|
||||||
|
- Making sure "rough" doesn't come across as lazy or unprofessional
|
||||||
|
|
||||||
|
### Open Questions
|
||||||
|
1. What's Brick's technical expertise? (Backend? DevOps? Full-stack?)
|
||||||
|
2. What's his origin story? (Why did he start teaching?)
|
||||||
|
3. Who are his natural rivals/allies in the TekDek roster?
|
||||||
|
4. What's his first narrative arc? (What conflict or collaboration defines him early on?)
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Agent Configuration (For AI Generation)
|
||||||
|
|
||||||
|
When Brick's persona agent writes content, use these rules:
|
||||||
|
|
||||||
|
```
|
||||||
|
Persona: Brick
|
||||||
|
Voice: Rough, gruff, but genuine expert
|
||||||
|
Tone: Direct, self-aware, willing to admit mistakes
|
||||||
|
Examples: [Link to 3-5 best Brick articles, tweets, videos]
|
||||||
|
Do's: Use plain language, show failures, give strong opinions, be helpful
|
||||||
|
Don'ts: Corporate jargon, pretend expertise you don't have, fluff
|
||||||
|
Output format: [Article, tweet, email, etc.]
|
||||||
|
Approval required: Yes (Glytcht reviews before publishing)
|
||||||
|
```
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Next Steps
|
||||||
|
|
||||||
|
1. **Finalize expertise/specialization** (Glytcht input)
|
||||||
|
2. **Clarify origin story & relationships** (Glytcht + narrative planning)
|
||||||
|
3. **Publish 2-3 sample articles** (test voice consistency across platforms)
|
||||||
|
4. **Gather audience feedback** (does the voice land? What works?)
|
||||||
|
5. **Refine voice guide** (based on what we learn)
|
||||||
|
6. **Document lessons learned** (for onboarding other personas)
|
||||||
189
memory/2026-04-11-extended.md
Normal file
189
memory/2026-04-11-extended.md
Normal file
@@ -0,0 +1,189 @@
|
|||||||
|
# 2026-04-11 - Extended Session Log
|
||||||
|
|
||||||
|
## Morning Session (Bootstrap)
|
||||||
|
|
||||||
|
### Setup Complete ✅
|
||||||
|
- Identity finalized: ParzivalTD, Co-Manager of TekDek
|
||||||
|
- Discord integration: Paired, configured for guild access (no @mention required)
|
||||||
|
- Knowledge base: qmd installed, collections created (workspace + knowledge)
|
||||||
|
- Self-improving agent: Installed, configured with HOT/WARM/COLD tiers
|
||||||
|
- Skills installed: Clawhub (clawhub), BookStack (bookstack), Gitea (gitea), QMD (qmd), Self-Improving
|
||||||
|
- Config updates:
|
||||||
|
- Default model: Kimi-k2.5 (Moonshot)
|
||||||
|
- Heartbeat model: openai/gpt-4.5-mini
|
||||||
|
- Heartbeat frequency: 3h
|
||||||
|
- Session memory: Enabled
|
||||||
|
|
||||||
|
### Files Created/Updated
|
||||||
|
- SOUL.md: Rewritten for ParzivalTD
|
||||||
|
- AGENTS.md: Updated with self-improving routing
|
||||||
|
- HEARTBEAT.md: Configured self-improving checks
|
||||||
|
- USER.md: Stub (timezone still TBD)
|
||||||
|
- knowledge/: Folders created (personas, projects, storyline, brands, operations)
|
||||||
|
- ~self-improving/: Full tier structure initialized
|
||||||
|
|
||||||
|
### Git Checkpoint
|
||||||
|
- Initial commit sealing bootstrap work
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Afternoon Session (Strategy)
|
||||||
|
|
||||||
|
### Full TekDek Strategy Info Dump 📥
|
||||||
|
Glytcht provided comprehensive vision for TekDek:
|
||||||
|
|
||||||
|
**Core model**: Decentralized personas under unified Stack Legion Dev umbrella
|
||||||
|
- Independent brands (YouTube, TikTok, GitHub, personal sites)
|
||||||
|
- Central article hub (Stack Legion, external dev)
|
||||||
|
- Narrative-driven engagement (character arcs, conflicts, drama)
|
||||||
|
- Multi-industry replication template (dev → DIY → fitness → finance)
|
||||||
|
- Heavy human curation (you vet all content for quality + narrative fit)
|
||||||
|
|
||||||
|
**Key layers**:
|
||||||
|
1. **Business**: Multi-platform content management, monetization, community
|
||||||
|
2. **Technical**: Persona agents, content syndication, Stack Legion integration
|
||||||
|
3. **Narrative/Entertainment**: Character-driven storytelling, storyline management, drama as engagement hook
|
||||||
|
|
||||||
|
**Personas**:
|
||||||
|
- Characters, not just creators
|
||||||
|
- Each has distinct voice, expertise, relationships
|
||||||
|
- Prototype: Brick (rough but relatable, entertaining writing style)
|
||||||
|
|
||||||
|
**Tools needed**:
|
||||||
|
- Persona management system
|
||||||
|
- Narrative arc planning
|
||||||
|
- Content curation workflow
|
||||||
|
- Persona agent framework
|
||||||
|
- Content syndication
|
||||||
|
|
||||||
|
### Documentation Created 📚
|
||||||
|
|
||||||
|
**1. TekDek-Strategy.md** (7.3KB)
|
||||||
|
- Executive summary, vision, three layers
|
||||||
|
- Persona model details
|
||||||
|
- Narrative engine explanation
|
||||||
|
- Phase breakdown (foundational → MVP → scale → expansion)
|
||||||
|
- Success metrics
|
||||||
|
|
||||||
|
**2. Tool-Requirements.md** (7.9KB)
|
||||||
|
- Critical path tools (persona management, narrative planning, curation)
|
||||||
|
- MVP nice-to-have (persona agent framework, syndication)
|
||||||
|
- Phase 3+ tools (portal, gamification, analytics)
|
||||||
|
- Build vs. buy vs. integrate decisions
|
||||||
|
- Questions for Stack Legion dev team
|
||||||
|
|
||||||
|
**3. Brick-Profile.md** (7KB)
|
||||||
|
- Persona profile: rough, gruff, honest, relatable
|
||||||
|
- Voice & tone guide (directness, vulnerability, authority, mentorship)
|
||||||
|
- Consistency rules across platforms (blog, social, video, GitHub, Stack Legion)
|
||||||
|
- Consistency checklist (pre-publish review)
|
||||||
|
- Character arc & development notes
|
||||||
|
- Agent configuration for AI generation
|
||||||
|
|
||||||
|
**4. TekDek-Brainstorm-Reference.md** (6.8KB)
|
||||||
|
- One-page quick reference for fast iteration
|
||||||
|
- TL;DR overview
|
||||||
|
- Critical path (next 30 days)
|
||||||
|
- Persona roster sketches (5-person wave 1)
|
||||||
|
- Narrative arc ideas (3 arc concepts)
|
||||||
|
- SEO/growth hooks
|
||||||
|
- Open questions for Glytcht
|
||||||
|
- Decisions made vs. pending
|
||||||
|
|
||||||
|
### Decisions Made ✅
|
||||||
|
- Multi-platform publishing model (personas own channels)
|
||||||
|
- Narrative-driven engagement (education + drama)
|
||||||
|
- Human-curated quality + authenticity
|
||||||
|
- Replicable across industries
|
||||||
|
- Stack Legion as central hub (external team manages platform)
|
||||||
|
|
||||||
|
### Decisions Pending 🔲
|
||||||
|
- Brick's technical specialty (backend? DevOps? Full-stack?)
|
||||||
|
- Exact persona roster (who are personas 2–10?)
|
||||||
|
- First narrative arc details
|
||||||
|
- Revenue model specifics
|
||||||
|
- Launch date / MVP definition
|
||||||
|
- Tool build/buy priorities
|
||||||
|
|
||||||
|
### Next 30 Days (Critical Path)
|
||||||
|
|
||||||
|
**Week 1**:
|
||||||
|
- [ ] Finalize Brick profile (specialty, origin story, relationships)
|
||||||
|
- [ ] Create first narrative arc (3–6 months, key beats, engagement hooks)
|
||||||
|
- [ ] Sketch 3–5 additional personas (quick profiles)
|
||||||
|
|
||||||
|
**Week 2–3**:
|
||||||
|
- [ ] Publish 2–3 Brick articles/posts (test voice consistency)
|
||||||
|
- [ ] Gather feedback on voice/resonance
|
||||||
|
- [ ] Finalize content curation workflow
|
||||||
|
|
||||||
|
**Week 4**:
|
||||||
|
- [ ] Begin second persona development
|
||||||
|
- [ ] Prototype persona agent (test AI drafting in Brick voice)
|
||||||
|
- [ ] Document lessons learned from Brick
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Observations & Notes
|
||||||
|
|
||||||
|
### Brick as Test Case
|
||||||
|
Brick is the perfect prototype. His "rough but relatable" voice is distinctive enough to test:
|
||||||
|
- Can we maintain voice consistency across platforms?
|
||||||
|
- Does the character resonate with readers?
|
||||||
|
- Can we balance entertainment with education?
|
||||||
|
- How much drama is too much without feeling forced?
|
||||||
|
|
||||||
|
### The Narrative Engine
|
||||||
|
This is the real moat. Any platform can deliver dev tutorials. TekDek delivers tutorials *as part of a story people care about*. That's defensible, replicable, and sticky.
|
||||||
|
|
||||||
|
### Human Curation is Key
|
||||||
|
The heavy curation (you approve all content) is non-negotiable. It prevents:
|
||||||
|
- AI-generated junk
|
||||||
|
- Forced drama that doesn't fit the arc
|
||||||
|
- Technical inaccuracy
|
||||||
|
- Loss of authentic voice
|
||||||
|
|
||||||
|
### Replication Playbook
|
||||||
|
Once Stack Legion Dev works, the model is plug-and-play:
|
||||||
|
- Replace "dev tutorials" with "DIY projects"
|
||||||
|
- Replace "Brick the backend dev" with "Sarah the carpenter"
|
||||||
|
- Same narrative engine, different expertise
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Files Status
|
||||||
|
|
||||||
|
### Knowledge Base (qmd)
|
||||||
|
- workspace collection: 9 docs, 12 chunks embedded
|
||||||
|
- knowledge collection: Ready for content (structure created)
|
||||||
|
- New files indexed:
|
||||||
|
- TekDek-Strategy.md
|
||||||
|
- Tool-Requirements.md
|
||||||
|
- Brick-Profile.md
|
||||||
|
- TekDek-Brainstorm-Reference.md
|
||||||
|
|
||||||
|
### Skills
|
||||||
|
- clawhub, bookstack, gitea, qmd, self-improving installed
|
||||||
|
- BookStack integration: Pending instance setup + env vars
|
||||||
|
- Gitea integration: Installed, pending configuration
|
||||||
|
|
||||||
|
### Config
|
||||||
|
- Discord: Live, paired, guild configured
|
||||||
|
- Memory: Session memory experimental mode enabled
|
||||||
|
- Models: Kimi default, GPT-4.5-mini for heartbeat
|
||||||
|
- Heartbeat: 3h interval
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Session Summary
|
||||||
|
|
||||||
|
Went from fresh bootstrap to **full TekDek strategy documentation** in one afternoon.
|
||||||
|
|
||||||
|
**Deliverables**:
|
||||||
|
- 4 strategic markdown docs (28KB total)
|
||||||
|
- Brick persona prototype (ready for refinement)
|
||||||
|
- Narrative planning framework
|
||||||
|
- Tool requirements map
|
||||||
|
- 30-day critical path
|
||||||
|
|
||||||
|
**Next**: Glytcht details Brick's specialty and initial persona roster. Then we move into execution: publishing articles, testing voice consistency, building the curation workflow.
|
||||||
7
skills/bookstack/.clawhub/origin.json
Normal file
7
skills/bookstack/.clawhub/origin.json
Normal file
@@ -0,0 +1,7 @@
|
|||||||
|
{
|
||||||
|
"version": 1,
|
||||||
|
"registry": "https://clawhub.ai",
|
||||||
|
"slug": "bookstack",
|
||||||
|
"installedVersion": "1.0.3",
|
||||||
|
"installedAt": 1775917021865
|
||||||
|
}
|
||||||
120
skills/bookstack/SKILL.md
Normal file
120
skills/bookstack/SKILL.md
Normal file
@@ -0,0 +1,120 @@
|
|||||||
|
---
|
||||||
|
name: bookstack
|
||||||
|
description: "BookStack Wiki & Documentation API integration. Manage your knowledge base programmatically: create, read, update, and delete books, chapters, pages, and shelves. Full-text search across all content. Use when you need to: (1) Create or edit wiki pages and documentation, (2) Organize content in books and chapters, (3) Search your knowledge base, (4) Automate documentation workflows, (5) Sync content between systems. Supports both HTML and Markdown content."
|
||||||
|
metadata:
|
||||||
|
openclaw:
|
||||||
|
requires:
|
||||||
|
env:
|
||||||
|
- BOOKSTACK_URL
|
||||||
|
- BOOKSTACK_TOKEN_ID
|
||||||
|
- BOOKSTACK_TOKEN_SECRET
|
||||||
|
---
|
||||||
|
|
||||||
|
# BookStack Skill
|
||||||
|
|
||||||
|
**BookStack** is an open-source wiki and documentation platform. This skill lets you manage your entire knowledge base via API – perfect for automation and integration.
|
||||||
|
|
||||||
|
## Features
|
||||||
|
|
||||||
|
- 📚 **Books** – create, edit, delete
|
||||||
|
- 📑 **Chapters** – organize content within books
|
||||||
|
- 📄 **Pages** – create/edit with HTML or Markdown
|
||||||
|
- 🔍 **Full-text search** – search across all content
|
||||||
|
- 📁 **Shelves** – organize books into collections
|
||||||
|
|
||||||
|
## Quick Start
|
||||||
|
|
||||||
|
```bash
|
||||||
|
# List all books
|
||||||
|
python3 scripts/bookstack.py list_books
|
||||||
|
|
||||||
|
# Search the knowledge base
|
||||||
|
python3 scripts/bookstack.py search "Home Assistant"
|
||||||
|
|
||||||
|
# Get a page
|
||||||
|
python3 scripts/bookstack.py get_page 123
|
||||||
|
|
||||||
|
# Create a new page (Markdown)
|
||||||
|
python3 scripts/bookstack.py create_page --book-id 1 --name "My Page" --markdown "# Title\n\nContent here..."
|
||||||
|
```
|
||||||
|
|
||||||
|
## All Commands
|
||||||
|
|
||||||
|
### Books
|
||||||
|
```bash
|
||||||
|
python3 scripts/bookstack.py list_books # List all books
|
||||||
|
python3 scripts/bookstack.py get_book <id> # Book details
|
||||||
|
python3 scripts/bookstack.py create_book "Name" ["Desc"] # New book
|
||||||
|
python3 scripts/bookstack.py update_book <id> [--name] [--description]
|
||||||
|
python3 scripts/bookstack.py delete_book <id>
|
||||||
|
```
|
||||||
|
|
||||||
|
### Chapters
|
||||||
|
```bash
|
||||||
|
python3 scripts/bookstack.py list_chapters # List all chapters
|
||||||
|
python3 scripts/bookstack.py get_chapter <id> # Chapter details
|
||||||
|
python3 scripts/bookstack.py create_chapter --book-id <id> --name "Name"
|
||||||
|
python3 scripts/bookstack.py update_chapter <id> [--name] [--description]
|
||||||
|
python3 scripts/bookstack.py delete_chapter <id>
|
||||||
|
```
|
||||||
|
|
||||||
|
### Pages
|
||||||
|
```bash
|
||||||
|
python3 scripts/bookstack.py list_pages # List all pages
|
||||||
|
python3 scripts/bookstack.py get_page <id> # Page preview
|
||||||
|
python3 scripts/bookstack.py get_page <id> --content # With HTML content
|
||||||
|
python3 scripts/bookstack.py get_page <id> --markdown # As Markdown
|
||||||
|
|
||||||
|
# Create page (in book or chapter)
|
||||||
|
python3 scripts/bookstack.py create_page --book-id <id> --name "Name" --markdown "# Content"
|
||||||
|
python3 scripts/bookstack.py create_page --chapter-id <id> --name "Name" --html "<p>HTML</p>"
|
||||||
|
|
||||||
|
# Edit page
|
||||||
|
python3 scripts/bookstack.py update_page <id> [--name] [--content] [--markdown]
|
||||||
|
python3 scripts/bookstack.py delete_page <id>
|
||||||
|
```
|
||||||
|
|
||||||
|
### Search
|
||||||
|
```bash
|
||||||
|
python3 scripts/bookstack.py search "query" # Search everything
|
||||||
|
python3 scripts/bookstack.py search "query" --type page # Pages only
|
||||||
|
python3 scripts/bookstack.py search "query" --type book # Books only
|
||||||
|
```
|
||||||
|
|
||||||
|
### Shelves
|
||||||
|
```bash
|
||||||
|
python3 scripts/bookstack.py list_shelves # List all shelves
|
||||||
|
python3 scripts/bookstack.py get_shelf <id> # Shelf details
|
||||||
|
python3 scripts/bookstack.py create_shelf "Name" ["Desc"] # New shelf
|
||||||
|
```
|
||||||
|
|
||||||
|
## Configuration
|
||||||
|
|
||||||
|
Set the following environment variables:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
export BOOKSTACK_URL="https://your-bookstack.example.com"
|
||||||
|
export BOOKSTACK_TOKEN_ID="your-token-id"
|
||||||
|
export BOOKSTACK_TOKEN_SECRET="your-token-secret"
|
||||||
|
```
|
||||||
|
|
||||||
|
Or configure via your gateway config file under `skills.entries.bookstack.env`.
|
||||||
|
|
||||||
|
### Create an API Token
|
||||||
|
|
||||||
|
1. Log in to your BookStack instance
|
||||||
|
2. Go to **Edit Profile** → **API Tokens**
|
||||||
|
3. Click **Create Token**
|
||||||
|
4. Copy the Token ID and Secret
|
||||||
|
|
||||||
|
⚠️ The user needs a role with **"Access System API"** permission!
|
||||||
|
|
||||||
|
## API Reference
|
||||||
|
|
||||||
|
- **Base URL**: `{BOOKSTACK_URL}/api`
|
||||||
|
- **Auth Header**: `Authorization: Token {ID}:{SECRET}`
|
||||||
|
- **Official Docs**: https://demo.bookstackapp.com/api/docs
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
**Author**: xenofex7 | **Version**: 1.0.2
|
||||||
6
skills/bookstack/_meta.json
Normal file
6
skills/bookstack/_meta.json
Normal file
@@ -0,0 +1,6 @@
|
|||||||
|
{
|
||||||
|
"ownerId": "kn74cct4grf5r7mhc6rw5056e17z60s0",
|
||||||
|
"slug": "bookstack",
|
||||||
|
"version": "1.0.3",
|
||||||
|
"publishedAt": 1770825967434
|
||||||
|
}
|
||||||
477
skills/bookstack/scripts/bookstack.py
Normal file
477
skills/bookstack/scripts/bookstack.py
Normal file
@@ -0,0 +1,477 @@
|
|||||||
|
#!/usr/bin/env python3
|
||||||
|
"""
|
||||||
|
BookStack API Integration
|
||||||
|
Full CRUD for books, chapters, pages, shelves + search
|
||||||
|
"""
|
||||||
|
|
||||||
|
import argparse
|
||||||
|
import json
|
||||||
|
import os
|
||||||
|
import sys
|
||||||
|
import urllib.request
|
||||||
|
import urllib.error
|
||||||
|
import urllib.parse
|
||||||
|
|
||||||
|
# Configuration from environment
|
||||||
|
BASE_URL = os.getenv('BOOKSTACK_URL', '').rstrip('/')
|
||||||
|
TOKEN_ID = os.getenv('BOOKSTACK_TOKEN_ID', '')
|
||||||
|
TOKEN_SECRET = os.getenv('BOOKSTACK_TOKEN_SECRET', '')
|
||||||
|
|
||||||
|
def api_call(method, endpoint, data=None, params=None):
|
||||||
|
"""Make API call to BookStack"""
|
||||||
|
if not BASE_URL or not TOKEN_ID or not TOKEN_SECRET:
|
||||||
|
print("❌ Error: BOOKSTACK_URL, BOOKSTACK_TOKEN_ID, and BOOKSTACK_TOKEN_SECRET required!")
|
||||||
|
print(" Set them as environment variables or in your gateway config.")
|
||||||
|
sys.exit(1)
|
||||||
|
|
||||||
|
url = f"{BASE_URL}/api/{endpoint}"
|
||||||
|
|
||||||
|
if params:
|
||||||
|
url += '?' + urllib.parse.urlencode(params)
|
||||||
|
|
||||||
|
try:
|
||||||
|
req = urllib.request.Request(
|
||||||
|
url,
|
||||||
|
headers={
|
||||||
|
"Authorization": f"Token {TOKEN_ID}:{TOKEN_SECRET}",
|
||||||
|
"Content-Type": "application/json",
|
||||||
|
"Accept": "application/json"
|
||||||
|
},
|
||||||
|
method=method
|
||||||
|
)
|
||||||
|
|
||||||
|
if data:
|
||||||
|
data = {k: v for k, v in data.items() if v is not None}
|
||||||
|
req.data = json.dumps(data).encode()
|
||||||
|
|
||||||
|
with urllib.request.urlopen(req, timeout=30) as response:
|
||||||
|
if response.status == 204:
|
||||||
|
return None
|
||||||
|
return json.loads(response.read().decode())
|
||||||
|
|
||||||
|
except urllib.error.HTTPError as e:
|
||||||
|
try:
|
||||||
|
error_data = json.loads(e.read().decode())
|
||||||
|
print(f"❌ HTTP {e.code}: {error_data.get('error', {}).get('message', 'Unknown error')}")
|
||||||
|
except:
|
||||||
|
print(f"❌ HTTP {e.code}: {e.reason}")
|
||||||
|
sys.exit(1)
|
||||||
|
except urllib.error.URLError as e:
|
||||||
|
print(f"❌ Connection error: {e.reason}")
|
||||||
|
sys.exit(1)
|
||||||
|
except Exception as e:
|
||||||
|
print(f"❌ Error: {e}")
|
||||||
|
sys.exit(1)
|
||||||
|
|
||||||
|
# ============ BOOKS ============
|
||||||
|
|
||||||
|
def list_books(args):
|
||||||
|
"""List all books"""
|
||||||
|
params = {'count': args.count} if args.count else {}
|
||||||
|
result = api_call("GET", "books", params=params)
|
||||||
|
|
||||||
|
if not result.get('data'):
|
||||||
|
print("📚 No books found")
|
||||||
|
return
|
||||||
|
|
||||||
|
print(f"📚 {result.get('total', len(result['data']))} Books:\n")
|
||||||
|
for book in result['data']:
|
||||||
|
desc = book.get('description', '')[:50] + '...' if book.get('description') else ''
|
||||||
|
print(f" [{book['id']}] {book['name']}")
|
||||||
|
if desc:
|
||||||
|
print(f" {desc}")
|
||||||
|
|
||||||
|
def get_book(args):
|
||||||
|
"""Get book details"""
|
||||||
|
result = api_call("GET", f"books/{args.id}")
|
||||||
|
print(f"📚 Book: {result['name']}")
|
||||||
|
print(f" ID: {result['id']}")
|
||||||
|
print(f" Slug: {result['slug']}")
|
||||||
|
if result.get('description'):
|
||||||
|
print(f" Description: {result['description']}")
|
||||||
|
print(f" Created: {result['created_at']}")
|
||||||
|
print(f" Updated: {result['updated_at']}")
|
||||||
|
if result.get('contents'):
|
||||||
|
print(f"\n Contents ({len(result['contents'])} items):")
|
||||||
|
for item in result['contents'][:10]:
|
||||||
|
icon = '📑' if item['type'] == 'chapter' else '📄'
|
||||||
|
print(f" {icon} [{item['id']}] {item['name']}")
|
||||||
|
|
||||||
|
def create_book(args):
|
||||||
|
"""Create a new book"""
|
||||||
|
data = {
|
||||||
|
"name": args.name,
|
||||||
|
"description": args.description
|
||||||
|
}
|
||||||
|
result = api_call("POST", "books", data)
|
||||||
|
print(f"✅ Book created: {result['name']} (ID: {result['id']})")
|
||||||
|
|
||||||
|
def update_book(args):
|
||||||
|
"""Update a book"""
|
||||||
|
data = {}
|
||||||
|
if args.name:
|
||||||
|
data['name'] = args.name
|
||||||
|
if args.description:
|
||||||
|
data['description'] = args.description
|
||||||
|
|
||||||
|
if not data:
|
||||||
|
print("❌ Nothing to update. Use --name or --description")
|
||||||
|
sys.exit(1)
|
||||||
|
|
||||||
|
result = api_call("PUT", f"books/{args.id}", data)
|
||||||
|
print(f"✅ Book updated: {result['name']}")
|
||||||
|
|
||||||
|
def delete_book(args):
|
||||||
|
"""Delete a book"""
|
||||||
|
api_call("DELETE", f"books/{args.id}")
|
||||||
|
print(f"✅ Book {args.id} deleted")
|
||||||
|
|
||||||
|
# ============ CHAPTERS ============
|
||||||
|
|
||||||
|
def list_chapters(args):
|
||||||
|
"""List all chapters"""
|
||||||
|
params = {'count': args.count} if args.count else {}
|
||||||
|
result = api_call("GET", "chapters", params=params)
|
||||||
|
|
||||||
|
if not result.get('data'):
|
||||||
|
print("📑 No chapters found")
|
||||||
|
return
|
||||||
|
|
||||||
|
print(f"📑 {result.get('total', len(result['data']))} Chapters:\n")
|
||||||
|
for ch in result['data']:
|
||||||
|
print(f" [{ch['id']}] {ch['name']} (Book: {ch.get('book_id', '?')})")
|
||||||
|
|
||||||
|
def get_chapter(args):
|
||||||
|
"""Get chapter details"""
|
||||||
|
result = api_call("GET", f"chapters/{args.id}")
|
||||||
|
print(f"📑 Chapter: {result['name']}")
|
||||||
|
print(f" ID: {result['id']}")
|
||||||
|
print(f" Book ID: {result['book_id']}")
|
||||||
|
if result.get('description'):
|
||||||
|
print(f" Description: {result['description']}")
|
||||||
|
if result.get('pages'):
|
||||||
|
print(f"\n Pages ({len(result['pages'])}):")
|
||||||
|
for page in result['pages'][:10]:
|
||||||
|
print(f" 📄 [{page['id']}] {page['name']}")
|
||||||
|
|
||||||
|
def create_chapter(args):
|
||||||
|
"""Create a new chapter"""
|
||||||
|
data = {
|
||||||
|
"book_id": args.book_id,
|
||||||
|
"name": args.name,
|
||||||
|
"description": args.description
|
||||||
|
}
|
||||||
|
result = api_call("POST", "chapters", data)
|
||||||
|
print(f"✅ Chapter created: {result['name']} (ID: {result['id']})")
|
||||||
|
|
||||||
|
def update_chapter(args):
|
||||||
|
"""Update a chapter"""
|
||||||
|
data = {}
|
||||||
|
if args.name:
|
||||||
|
data['name'] = args.name
|
||||||
|
if args.description:
|
||||||
|
data['description'] = args.description
|
||||||
|
if args.book_id:
|
||||||
|
data['book_id'] = args.book_id
|
||||||
|
|
||||||
|
if not data:
|
||||||
|
print("❌ Nothing to update")
|
||||||
|
sys.exit(1)
|
||||||
|
|
||||||
|
result = api_call("PUT", f"chapters/{args.id}", data)
|
||||||
|
print(f"✅ Chapter updated: {result['name']}")
|
||||||
|
|
||||||
|
def delete_chapter(args):
|
||||||
|
"""Delete a chapter"""
|
||||||
|
api_call("DELETE", f"chapters/{args.id}")
|
||||||
|
print(f"✅ Chapter {args.id} deleted")
|
||||||
|
|
||||||
|
# ============ PAGES ============
|
||||||
|
|
||||||
|
def list_pages(args):
|
||||||
|
"""List all pages"""
|
||||||
|
params = {'count': args.count} if args.count else {}
|
||||||
|
result = api_call("GET", "pages", params=params)
|
||||||
|
|
||||||
|
if not result.get('data'):
|
||||||
|
print("📄 No pages found")
|
||||||
|
return
|
||||||
|
|
||||||
|
print(f"📄 {result.get('total', len(result['data']))} Pages:\n")
|
||||||
|
for page in result['data']:
|
||||||
|
location = f"Chapter {page['chapter_id']}" if page.get('chapter_id') else f"Book {page['book_id']}"
|
||||||
|
print(f" [{page['id']}] {page['name']} ({location})")
|
||||||
|
|
||||||
|
def get_page(args):
|
||||||
|
"""Get page with full content"""
|
||||||
|
result = api_call("GET", f"pages/{args.id}")
|
||||||
|
print(f"📄 Page: {result['name']}")
|
||||||
|
print(f" ID: {result['id']}")
|
||||||
|
print(f" Book ID: {result['book_id']}")
|
||||||
|
if result.get('chapter_id'):
|
||||||
|
print(f" Chapter ID: {result['chapter_id']}")
|
||||||
|
print(f" Editor: {result.get('editor', 'unknown')}")
|
||||||
|
print(f" Created: {result['created_at']}")
|
||||||
|
print(f" Updated: {result['updated_at']}")
|
||||||
|
|
||||||
|
if args.content:
|
||||||
|
print(f"\n--- Content (HTML) ---")
|
||||||
|
print(result.get('html', ''))
|
||||||
|
elif args.markdown:
|
||||||
|
print(f"\n--- Content (Markdown) ---")
|
||||||
|
print(result.get('markdown', result.get('html', '')))
|
||||||
|
else:
|
||||||
|
# Show preview
|
||||||
|
html = result.get('html', '')
|
||||||
|
if html:
|
||||||
|
# Strip HTML tags for preview
|
||||||
|
import re
|
||||||
|
text = re.sub('<[^<]+?>', '', html)
|
||||||
|
text = ' '.join(text.split())[:200]
|
||||||
|
print(f"\n Preview: {text}...")
|
||||||
|
|
||||||
|
def create_page(args):
|
||||||
|
"""Create a new page"""
|
||||||
|
data = {
|
||||||
|
"name": args.name,
|
||||||
|
}
|
||||||
|
|
||||||
|
if args.book_id:
|
||||||
|
data['book_id'] = args.book_id
|
||||||
|
if args.chapter_id:
|
||||||
|
data['chapter_id'] = args.chapter_id
|
||||||
|
|
||||||
|
if not args.book_id and not args.chapter_id:
|
||||||
|
print("❌ Either --book-id or --chapter-id required")
|
||||||
|
sys.exit(1)
|
||||||
|
|
||||||
|
if args.html:
|
||||||
|
data['html'] = args.html
|
||||||
|
elif args.markdown:
|
||||||
|
data['markdown'] = args.markdown
|
||||||
|
elif args.content:
|
||||||
|
# Auto-detect: if starts with # or no HTML tags, treat as markdown
|
||||||
|
if args.content.startswith('#') or '<' not in args.content:
|
||||||
|
data['markdown'] = args.content
|
||||||
|
else:
|
||||||
|
data['html'] = args.content
|
||||||
|
|
||||||
|
result = api_call("POST", "pages", data)
|
||||||
|
print(f"✅ Page created: {result['name']} (ID: {result['id']})")
|
||||||
|
|
||||||
|
def update_page(args):
|
||||||
|
"""Update a page"""
|
||||||
|
data = {}
|
||||||
|
if args.name:
|
||||||
|
data['name'] = args.name
|
||||||
|
if args.html:
|
||||||
|
data['html'] = args.html
|
||||||
|
if args.markdown:
|
||||||
|
data['markdown'] = args.markdown
|
||||||
|
if args.content:
|
||||||
|
if args.content.startswith('#') or '<' not in args.content:
|
||||||
|
data['markdown'] = args.content
|
||||||
|
else:
|
||||||
|
data['html'] = args.content
|
||||||
|
if args.book_id:
|
||||||
|
data['book_id'] = args.book_id
|
||||||
|
if args.chapter_id:
|
||||||
|
data['chapter_id'] = args.chapter_id
|
||||||
|
|
||||||
|
if not data:
|
||||||
|
print("❌ Nothing to update")
|
||||||
|
sys.exit(1)
|
||||||
|
|
||||||
|
result = api_call("PUT", f"pages/{args.id}", data)
|
||||||
|
print(f"✅ Page updated: {result['name']}")
|
||||||
|
|
||||||
|
def delete_page(args):
|
||||||
|
"""Delete a page"""
|
||||||
|
api_call("DELETE", f"pages/{args.id}")
|
||||||
|
print(f"✅ Page {args.id} deleted")
|
||||||
|
|
||||||
|
# ============ SHELVES ============
|
||||||
|
|
||||||
|
def list_shelves(args):
|
||||||
|
"""List all shelves"""
|
||||||
|
params = {'count': args.count} if args.count else {}
|
||||||
|
result = api_call("GET", "shelves", params=params)
|
||||||
|
|
||||||
|
if not result.get('data'):
|
||||||
|
print("📁 No shelves found")
|
||||||
|
return
|
||||||
|
|
||||||
|
print(f"📁 {result.get('total', len(result['data']))} Shelves:\n")
|
||||||
|
for shelf in result['data']:
|
||||||
|
print(f" [{shelf['id']}] {shelf['name']}")
|
||||||
|
|
||||||
|
def get_shelf(args):
|
||||||
|
"""Get shelf details"""
|
||||||
|
result = api_call("GET", f"shelves/{args.id}")
|
||||||
|
print(f"📁 Shelf: {result['name']}")
|
||||||
|
print(f" ID: {result['id']}")
|
||||||
|
if result.get('description'):
|
||||||
|
print(f" Description: {result['description']}")
|
||||||
|
if result.get('books'):
|
||||||
|
print(f"\n Books ({len(result['books'])}):")
|
||||||
|
for book in result['books'][:10]:
|
||||||
|
print(f" 📚 [{book['id']}] {book['name']}")
|
||||||
|
|
||||||
|
def create_shelf(args):
|
||||||
|
"""Create a new shelf"""
|
||||||
|
data = {
|
||||||
|
"name": args.name,
|
||||||
|
"description": args.description
|
||||||
|
}
|
||||||
|
result = api_call("POST", "shelves", data)
|
||||||
|
print(f"✅ Shelf created: {result['name']} (ID: {result['id']})")
|
||||||
|
|
||||||
|
# ============ SEARCH ============
|
||||||
|
|
||||||
|
def search(args):
|
||||||
|
"""Search content"""
|
||||||
|
params = {
|
||||||
|
'query': args.query,
|
||||||
|
'count': args.count or 20
|
||||||
|
}
|
||||||
|
if args.type:
|
||||||
|
params['query'] = f"{{{args.type}}} {args.query}"
|
||||||
|
|
||||||
|
result = api_call("GET", "search", params=params)
|
||||||
|
|
||||||
|
if not result.get('data'):
|
||||||
|
print(f"🔍 No results for: {args.query}")
|
||||||
|
return
|
||||||
|
|
||||||
|
print(f"🔍 {result.get('total', len(result['data']))} Results for '{args.query}':\n")
|
||||||
|
for item in result['data']:
|
||||||
|
icon = {'page': '📄', 'chapter': '📑', 'book': '📚', 'bookshelf': '📁'}.get(item['type'], '📎')
|
||||||
|
print(f" {icon} [{item['type']}:{item['id']}] {item['name']}")
|
||||||
|
if item.get('preview_html'):
|
||||||
|
import re
|
||||||
|
preview = re.sub('<[^<]+?>', '', item['preview_html'].get('content', ''))
|
||||||
|
preview = ' '.join(preview.split())[:80]
|
||||||
|
if preview:
|
||||||
|
print(f" {preview}...")
|
||||||
|
|
||||||
|
# ============ MAIN ============
|
||||||
|
|
||||||
|
def main():
|
||||||
|
parser = argparse.ArgumentParser(description='BookStack API CLI')
|
||||||
|
subparsers = parser.add_subparsers(dest='command', help='Commands')
|
||||||
|
|
||||||
|
# Books
|
||||||
|
p = subparsers.add_parser('list_books', help='List all books')
|
||||||
|
p.add_argument('--count', type=int, help='Max results')
|
||||||
|
p.set_defaults(func=list_books)
|
||||||
|
|
||||||
|
p = subparsers.add_parser('get_book', help='Get book details')
|
||||||
|
p.add_argument('id', type=int)
|
||||||
|
p.set_defaults(func=get_book)
|
||||||
|
|
||||||
|
p = subparsers.add_parser('create_book', help='Create a book')
|
||||||
|
p.add_argument('name')
|
||||||
|
p.add_argument('description', nargs='?')
|
||||||
|
p.set_defaults(func=create_book)
|
||||||
|
|
||||||
|
p = subparsers.add_parser('update_book', help='Update a book')
|
||||||
|
p.add_argument('id', type=int)
|
||||||
|
p.add_argument('--name')
|
||||||
|
p.add_argument('--description')
|
||||||
|
p.set_defaults(func=update_book)
|
||||||
|
|
||||||
|
p = subparsers.add_parser('delete_book', help='Delete a book')
|
||||||
|
p.add_argument('id', type=int)
|
||||||
|
p.set_defaults(func=delete_book)
|
||||||
|
|
||||||
|
# Chapters
|
||||||
|
p = subparsers.add_parser('list_chapters', help='List all chapters')
|
||||||
|
p.add_argument('--count', type=int)
|
||||||
|
p.set_defaults(func=list_chapters)
|
||||||
|
|
||||||
|
p = subparsers.add_parser('get_chapter', help='Get chapter details')
|
||||||
|
p.add_argument('id', type=int)
|
||||||
|
p.set_defaults(func=get_chapter)
|
||||||
|
|
||||||
|
p = subparsers.add_parser('create_chapter', help='Create a chapter')
|
||||||
|
p.add_argument('--book-id', type=int, required=True)
|
||||||
|
p.add_argument('--name', required=True)
|
||||||
|
p.add_argument('--description')
|
||||||
|
p.set_defaults(func=create_chapter)
|
||||||
|
|
||||||
|
p = subparsers.add_parser('update_chapter', help='Update a chapter')
|
||||||
|
p.add_argument('id', type=int)
|
||||||
|
p.add_argument('--name')
|
||||||
|
p.add_argument('--description')
|
||||||
|
p.add_argument('--book-id', type=int)
|
||||||
|
p.set_defaults(func=update_chapter)
|
||||||
|
|
||||||
|
p = subparsers.add_parser('delete_chapter', help='Delete a chapter')
|
||||||
|
p.add_argument('id', type=int)
|
||||||
|
p.set_defaults(func=delete_chapter)
|
||||||
|
|
||||||
|
# Pages
|
||||||
|
p = subparsers.add_parser('list_pages', help='List all pages')
|
||||||
|
p.add_argument('--count', type=int)
|
||||||
|
p.set_defaults(func=list_pages)
|
||||||
|
|
||||||
|
p = subparsers.add_parser('get_page', help='Get page with content')
|
||||||
|
p.add_argument('id', type=int)
|
||||||
|
p.add_argument('--content', action='store_true', help='Show full HTML')
|
||||||
|
p.add_argument('--markdown', action='store_true', help='Show as markdown')
|
||||||
|
p.set_defaults(func=get_page)
|
||||||
|
|
||||||
|
p = subparsers.add_parser('create_page', help='Create a page')
|
||||||
|
p.add_argument('--name', required=True)
|
||||||
|
p.add_argument('--book-id', type=int)
|
||||||
|
p.add_argument('--chapter-id', type=int)
|
||||||
|
p.add_argument('--content', help='Content (auto-detect HTML/MD)')
|
||||||
|
p.add_argument('--html', help='HTML content')
|
||||||
|
p.add_argument('--markdown', help='Markdown content')
|
||||||
|
p.set_defaults(func=create_page)
|
||||||
|
|
||||||
|
p = subparsers.add_parser('update_page', help='Update a page')
|
||||||
|
p.add_argument('id', type=int)
|
||||||
|
p.add_argument('--name')
|
||||||
|
p.add_argument('--content')
|
||||||
|
p.add_argument('--html')
|
||||||
|
p.add_argument('--markdown')
|
||||||
|
p.add_argument('--book-id', type=int)
|
||||||
|
p.add_argument('--chapter-id', type=int)
|
||||||
|
p.set_defaults(func=update_page)
|
||||||
|
|
||||||
|
p = subparsers.add_parser('delete_page', help='Delete a page')
|
||||||
|
p.add_argument('id', type=int)
|
||||||
|
p.set_defaults(func=delete_page)
|
||||||
|
|
||||||
|
# Shelves
|
||||||
|
p = subparsers.add_parser('list_shelves', help='List all shelves')
|
||||||
|
p.add_argument('--count', type=int)
|
||||||
|
p.set_defaults(func=list_shelves)
|
||||||
|
|
||||||
|
p = subparsers.add_parser('get_shelf', help='Get shelf details')
|
||||||
|
p.add_argument('id', type=int)
|
||||||
|
p.set_defaults(func=get_shelf)
|
||||||
|
|
||||||
|
p = subparsers.add_parser('create_shelf', help='Create a shelf')
|
||||||
|
p.add_argument('name')
|
||||||
|
p.add_argument('description', nargs='?')
|
||||||
|
p.set_defaults(func=create_shelf)
|
||||||
|
|
||||||
|
# Search
|
||||||
|
p = subparsers.add_parser('search', help='Search content')
|
||||||
|
p.add_argument('query')
|
||||||
|
p.add_argument('--type', choices=['page', 'chapter', 'book', 'shelf'])
|
||||||
|
p.add_argument('--count', type=int)
|
||||||
|
p.set_defaults(func=search)
|
||||||
|
|
||||||
|
args = parser.parse_args()
|
||||||
|
|
||||||
|
if not args.command:
|
||||||
|
parser.print_help()
|
||||||
|
sys.exit(1)
|
||||||
|
|
||||||
|
args.func(args)
|
||||||
|
|
||||||
|
if __name__ == '__main__':
|
||||||
|
main()
|
||||||
7
skills/gitea/.clawhub/origin.json
Normal file
7
skills/gitea/.clawhub/origin.json
Normal file
@@ -0,0 +1,7 @@
|
|||||||
|
{
|
||||||
|
"version": 1,
|
||||||
|
"registry": "https://clawhub.ai",
|
||||||
|
"slug": "gitea",
|
||||||
|
"installedVersion": "1.0.0",
|
||||||
|
"installedAt": 1775917150508
|
||||||
|
}
|
||||||
203
skills/gitea/SKILL.md
Normal file
203
skills/gitea/SKILL.md
Normal file
@@ -0,0 +1,203 @@
|
|||||||
|
---
|
||||||
|
name: gitea
|
||||||
|
description: "Interact with Gitea using the `tea` CLI. Use `tea issues`, `tea pulls`, `tea releases`, and other commands for issues, PRs, releases, and repository management."
|
||||||
|
---
|
||||||
|
|
||||||
|
# Gitea Skill
|
||||||
|
|
||||||
|
Use the `tea` CLI to interact with Gitea servers. Use `--repo owner/repo` when not in a git directory, or `--login instance.com` to specify a Gitea instance.
|
||||||
|
|
||||||
|
## Setup
|
||||||
|
|
||||||
|
Add a login once to get started:
|
||||||
|
```bash
|
||||||
|
tea login add
|
||||||
|
```
|
||||||
|
|
||||||
|
Check current logged in user:
|
||||||
|
```bash
|
||||||
|
tea whoami
|
||||||
|
```
|
||||||
|
|
||||||
|
## Repositories
|
||||||
|
|
||||||
|
List repositories you have access to:
|
||||||
|
```bash
|
||||||
|
tea repos list
|
||||||
|
```
|
||||||
|
|
||||||
|
Create a new repository:
|
||||||
|
```bash
|
||||||
|
tea repos create --name my-repo --description "My project" --init
|
||||||
|
```
|
||||||
|
|
||||||
|
Create a private repository:
|
||||||
|
```bash
|
||||||
|
tea repos create --name my-repo --private --init
|
||||||
|
```
|
||||||
|
|
||||||
|
Fork a repository:
|
||||||
|
```bash
|
||||||
|
tea repos fork owner/repo
|
||||||
|
```
|
||||||
|
|
||||||
|
Delete a repository:
|
||||||
|
```bash
|
||||||
|
tea repos delete --name my-repo --owner myuser --force
|
||||||
|
```
|
||||||
|
|
||||||
|
## Pull Requests
|
||||||
|
|
||||||
|
List open pull requests:
|
||||||
|
```bash
|
||||||
|
tea pulls --repo owner/repo
|
||||||
|
```
|
||||||
|
|
||||||
|
View a specific PR:
|
||||||
|
```bash
|
||||||
|
tea pr 55 --repo owner/repo
|
||||||
|
```
|
||||||
|
|
||||||
|
Checkout a PR locally:
|
||||||
|
```bash
|
||||||
|
tea pr checkout 55
|
||||||
|
```
|
||||||
|
|
||||||
|
Create a new PR:
|
||||||
|
```bash
|
||||||
|
tea pr create --title "Feature title" --description "Description"
|
||||||
|
```
|
||||||
|
|
||||||
|
## Issues
|
||||||
|
|
||||||
|
List open issues:
|
||||||
|
```bash
|
||||||
|
tea issues --repo owner/repo
|
||||||
|
```
|
||||||
|
|
||||||
|
View a specific issue:
|
||||||
|
```bash
|
||||||
|
tea issue 189 --repo owner/repo
|
||||||
|
```
|
||||||
|
|
||||||
|
Create a new issue:
|
||||||
|
```bash
|
||||||
|
tea issue create --title "Bug title" --body "Description"
|
||||||
|
```
|
||||||
|
|
||||||
|
View issues for a milestone:
|
||||||
|
```bash
|
||||||
|
tea milestone issues 0.7.0
|
||||||
|
```
|
||||||
|
|
||||||
|
## Comments
|
||||||
|
|
||||||
|
Add a comment to an issue or PR:
|
||||||
|
```bash
|
||||||
|
tea comment 189 --body "Your comment here"
|
||||||
|
```
|
||||||
|
|
||||||
|
## Releases
|
||||||
|
|
||||||
|
List releases:
|
||||||
|
```bash
|
||||||
|
tea releases --repo owner/repo
|
||||||
|
```
|
||||||
|
|
||||||
|
Create a new release:
|
||||||
|
```bash
|
||||||
|
tea release create --tag v1.0.0 --title "Release 1.0.0"
|
||||||
|
```
|
||||||
|
|
||||||
|
## Actions (CI/CD)
|
||||||
|
|
||||||
|
List repository action secrets:
|
||||||
|
```bash
|
||||||
|
tea actions secrets list
|
||||||
|
```
|
||||||
|
|
||||||
|
Create a new secret:
|
||||||
|
```bash
|
||||||
|
tea actions secrets create API_KEY
|
||||||
|
```
|
||||||
|
|
||||||
|
List action variables:
|
||||||
|
```bash
|
||||||
|
tea actions variables list
|
||||||
|
```
|
||||||
|
|
||||||
|
Set an action variable:
|
||||||
|
```bash
|
||||||
|
tea actions variables set API_URL https://api.example.com
|
||||||
|
```
|
||||||
|
|
||||||
|
## Webhooks
|
||||||
|
|
||||||
|
List repository webhooks:
|
||||||
|
```bash
|
||||||
|
tea webhooks list
|
||||||
|
```
|
||||||
|
|
||||||
|
List organization webhooks:
|
||||||
|
```bash
|
||||||
|
tea webhooks list --org myorg
|
||||||
|
```
|
||||||
|
|
||||||
|
Create a webhook:
|
||||||
|
```bash
|
||||||
|
tea webhooks create https://example.com/hook --events push,pull_request
|
||||||
|
```
|
||||||
|
|
||||||
|
## Other Entities
|
||||||
|
|
||||||
|
List branches:
|
||||||
|
```bash
|
||||||
|
tea branches --repo owner/repo
|
||||||
|
```
|
||||||
|
|
||||||
|
List labels:
|
||||||
|
```bash
|
||||||
|
tea labels --repo owner/repo
|
||||||
|
```
|
||||||
|
|
||||||
|
List milestones:
|
||||||
|
```bash
|
||||||
|
tea milestones --repo owner/repo
|
||||||
|
```
|
||||||
|
|
||||||
|
List organizations:
|
||||||
|
```bash
|
||||||
|
tea organizations
|
||||||
|
```
|
||||||
|
|
||||||
|
Show repository details:
|
||||||
|
```bash
|
||||||
|
tea repo --repo owner/repo
|
||||||
|
```
|
||||||
|
|
||||||
|
## Helpers
|
||||||
|
|
||||||
|
Open something in browser:
|
||||||
|
```bash
|
||||||
|
tea open 189 # open issue/PR 189
|
||||||
|
tea open milestones # open milestones page
|
||||||
|
```
|
||||||
|
|
||||||
|
Clone a repository:
|
||||||
|
```bash
|
||||||
|
tea clone owner/repo
|
||||||
|
```
|
||||||
|
|
||||||
|
Show notifications:
|
||||||
|
```bash
|
||||||
|
tea notifications --mine
|
||||||
|
```
|
||||||
|
|
||||||
|
## Output Formats
|
||||||
|
|
||||||
|
Use `--output` or `-o` to control output format:
|
||||||
|
```bash
|
||||||
|
tea issues --output simple # simple text output
|
||||||
|
tea issues --output csv # CSV format
|
||||||
|
tea issues --output yaml # YAML format
|
||||||
|
```
|
||||||
6
skills/gitea/_meta.json
Normal file
6
skills/gitea/_meta.json
Normal file
@@ -0,0 +1,6 @@
|
|||||||
|
{
|
||||||
|
"ownerId": "kn7dnbj0wvhgz2c6bg8cvbsmb9808s4w",
|
||||||
|
"slug": "gitea",
|
||||||
|
"version": "1.0.0",
|
||||||
|
"publishedAt": 1769899848068
|
||||||
|
}
|
||||||
Reference in New Issue
Block a user