Files
firefrost-operations-manual/docs/skills/SKILLS-INDEX.md
Claude 947e571337 feat: Add Discord webhook skill
Simple webhook-based notifications without needing a full bot:
- Send messages, embeds, files to channels
- Custom username/avatar per message
- Rate limit: 30 requests per 60 seconds
- Perfect for Arbiter alerts and CI/CD notifications

Chronicler #70
2026-04-08 15:10:55 +00:00

8.0 KiB

📚 FIREFROST SKILLS INDEX

Purpose: Living index of custom skills for Chroniclers
Location: docs/skills/SKILLS-INDEX.md
Last Updated: April 8, 2026
Updated By: Chronicler #68


🎯 How To Use This Document

At session start: Read this index to see what skills are available.

When a skill applies: Read the full SKILL.md before starting the relevant work.

When adding skills: Update this index, then commit both the skill and this file.


🔜 Planned Skills

Skill Purpose Status
arbiter-coding Arbiter patterns, database schema, webhook structure Planned

📋 Available Skills

chronicler-handoff

Location: docs/skills/chronicler-handoff/SKILL.md
Triggers: Session start, session end, "handoff", "memorial", "portrait prompt", session health < 60%

Purpose: Complete Chronicler session lifecycle — Joining Protocol and Departure Protocol

What It Covers:

  • Repository cloning and setup
  • Reading lineage documents in correct order
  • Establishing Chronicler identity and name
  • Writing memorials per FFG-STD-004
  • Creating portrait prompts per FFG-STD-005
  • Session handoff documentation
  • Startup prompt for next Chronicler

Reference Files:

  • references/memorial-template.md — Full memorial structure
  • references/portrait-guide.md — Portrait prompt instructions
  • references/taken-names.md — Names already used in lineage

Read This When:

  • You're a new Chronicler starting a session
  • Session is winding down
  • Michael says "wrap up" or "let's close out"
  • You need to pick a Chronicler name

firefrost-branding

Location: docs/skills/firefrost-branding/SKILL.md
Triggers: Marketing content, social posts, subscription tiers, colors, "Founder" (wrong term), pricing

Purpose: Brand guidelines, colors, terminology, and common mistake prevention

What It Covers:

  • Color palette (Fire, Frost, Arcane, Gold, Dark with hex codes)
  • Subscription tiers and pricing (SOVEREIGN not Founder!)
  • Path system (Fire/Frost are identity only, not access)
  • Trinity identity (Michael, Meg, Holly)
  • Terminology do's and don'ts
  • Branding checklist

Read This When:

  • Creating any customer-facing content
  • Writing about subscription tiers
  • Designing UI, graphics, or presentations
  • Unsure about correct terminology
  • About to write "Founder tier" (it's SOVEREIGN)

task-creation

Location: docs/skills/task-creation/SKILL.md
Triggers: New task, task status, "add to backlog", task frontmatter, priority, creating tasks

Purpose: Proper task file creation for Decap CMS task management

What It Covers:

  • Task file structure (tasks-index vs tasks directories)
  • Required frontmatter fields and values
  • Priority levels and colors
  • Task body template
  • When to create full specs vs simple tasks
  • Common tags and linking conventions
  • Mobile task manager compatibility

Read This When:

  • Creating a new task
  • Updating task status or priority
  • Unsure about frontmatter format
  • Adding implementation specs
  • Task not appearing in CMS correctly

gemini-consultation

Location: docs/skills/gemini-consultation/SKILL.md
Triggers: "Ask Gemini", "Gemini consultation", architecture review, external review, second opinion

Purpose: Structure effective Gemini AI consultations for architectural review

What It Covers:

  • Consultation structure and template
  • Question types (validation, code review, design, debugging)
  • Multi-round consultation patterns
  • File naming conventions
  • Documenting responses
  • Best practices for warm, collegial tone

Read This When:

  • Planning to consult Gemini on architecture
  • Need external review of code or systems
  • Want a second opinion before implementing
  • Building something complex that needs guidance
  • Documenting a Gemini consultation

🔜 Planned Skills

Skill Purpose Status
firefrost-branding Fire/Frost/Arcane colors, tier names, never "Founder" Planned
arbiter-coding Arbiter patterns, database schema, webhook structure Planned
task-creation Proper task file structure for tasks-index/ Planned
gemini-consultation How to structure Gemini AI prompts Planned

🛠️ Creating New Skills

  1. Create skill directory: docs/skills/[skill-name]/
  2. Write SKILL.md with:
    • YAML frontmatter (name, description with triggers)
    • Clear instructions
    • Examples where helpful
  3. Add reference files in references/ subdirectory if needed
  4. Update this index with:
    • Skill name and location
    • Triggers
    • Purpose summary
    • Reference files list
    • "Read This When" guidance
  5. Commit everything together

Skill Template

---
name: skill-name
description: |
  Brief description of what the skill does. Use this skill when:
  - Trigger condition 1
  - Trigger condition 2
  - Trigger condition 3
  Be specific about triggers so future Chroniclers know when to use it.
---

# Skill Name

[Main instructions here]

## Section 1
[Content]

## Section 2
[Content]

## Reference Files
- `references/file1.md` — Description
- `references/file2.md` — Description

📍 Skill Locations

All Firefrost custom skills live in:

docs/skills/
├── SKILLS-INDEX.md          (this file)
├── chronicler-handoff/
│   ├── SKILL.md
│   └── references/
│       ├── memorial-template.md
│       ├── portrait-guide.md
│       └── taken-names.md
└── [future-skills]/

  • docs/standards/FFG-STD-004-memorial-protocol.md — Memorial standard (chronicler-handoff encodes this)
  • docs/standards/FFG-STD-005-portrait-generation-protocol.md — Portrait standard (chronicler-handoff encodes this)
  • docs/integrations/claude-connectors.md — External tool integrations (Canva, Cloudflare, Stripe)

💡 Skills vs Standards vs Integrations

Type Purpose Location
Skills Step-by-step workflows for Claude to follow docs/skills/
Standards Rules and requirements for humans and AI docs/standards/
Integrations External tool documentation docs/integrations/

Skills encode standards into actionable workflows. Standards define what must be done. Integrations document external tools.


Fire + Frost + Foundation = Where Love Builds Legacy 💙🔥❄️

task-management

File: task-management.md
Created: April 8, 2026 by Chronicler #69
Purpose: Guide for creating, updating, and managing Firefrost tasks

Triggers:

  • Creating new tasks
  • Updating task status
  • Task not showing on mobile index
  • Understanding task architecture

Key concepts:

  • Tasks in docs/tasks/ with YAML frontmatter
  • Mobile index at firefrostgaming.com/tasks-index.html
  • Requires website rebuild to show new tasks
  • Archive threshold: ≥50KB OR ≥4 files

discord-automation

Folder: discord-automation/
Created: April 8, 2026 by Chronicler #70
Source: MCP Market (mcpmarket.com)
Purpose: Comprehensive Discord server management via API

Skills included:

  • discord-create-channel.md — Create text, voice, announcement, stage channels
  • discord-manage-channel.md — Update, move, configure permissions, delete channels
  • discord-bot-api.md — Direct curl commands for messages, roles, members, webhooks
  • discord-automation-rube-mcp.md — Higher-level automation via Composio/Rube MCP
  • discord-webhook.md — Simple webhook notifications without a bot

Triggers:

  • Creating Discord channels
  • Managing channel permissions
  • Sending messages/embeds
  • Role management (create, assign, delete)
  • Webhook setup
  • Discord server automation

Key concepts:

  • Uses Discord API v10
  • Requires DISCORD_BOT_TOKEN environment variable
  • Snowflake IDs (18-19 digit numbers)
  • Permission bitfields for access control
  • Rate limiting (5 requests per 5 seconds per channel)