go-go-golems
11 verified skills498 total stars
ttmp/_guidelines
# Guidelines: Skill Documents ## Purpose Skills are **disciplined workflows** written as documents (`DocType: skill`) that teach LLMs (and humans) *how to work*, not just what exists. A good skill turns “best practice” into a repeatable, enforceable process. Skills are meant to be discoverable via: - `docmgr skill list` (filter by topics, file/dir, ticket) - `docmgr skill show <query>` (load and apply a skill) ## Required Elements - **Frontmatter contract** - `DocType: skill` - `Title`: U
development84
ttmp/_templates
--- Title: {{TITLE}} Ticket: {{TICKET}} Status: draft Topics: {{TOPICS}} DocType: skill Intent: long-term Owners: {{OWNERS}} RelatedFiles: [] ExternalSources: [] Summary: > {{SUMMARY}} LastUpdated: {{DATE}} WhatFor: > <!-- 2–5 sentences: what outcome does this workflow enforce? --> WhenToUse: > <!-- Trigger conditions: "Use when ..." --> --- # {{TITLE}} ## Overview <!-- 2–5 sentences: why this skill matters and what it enforces --> ## When to Use <!-- concrete triggers + examples -->
documentation84
inference-smoke-tests
Run repeatable inference smoke tests using geppetto/pinocchio example binaries (single-pass, streaming, tool-loop, OpenAI Responses thinking) including tmux-driven TUI tests. Use when refactors touch InferenceState/Session/EngineBuilder, tool calling loop, event sinks, provider request formatting, or when you need a quick 'does inference still work?' checklist.
tools84
ttmp/_guidelines
# Guidelines: Skill Documents ## Purpose Skills are **disciplined workflows** written as documents (`DocType: skill`) that teach LLMs (and humans) *how to work*, not just what exists. A good skill turns “best practice” into a repeatable, enforceable process. Skills are meant to be discoverable via: - `docmgr skill list` (filter by topics, file/dir, ticket) - `docmgr skill show <query>` (load and apply a skill) ## Required Elements - **Frontmatter contract** - `DocType: skill` - `Title`: U
development58
ttmp/_templates
--- Title: {{TITLE}} Ticket: {{TICKET}} Status: draft Topics: {{TOPICS}} DocType: skill Intent: long-term Owners: {{OWNERS}} RelatedFiles: [] ExternalSources: [] Summary: > {{SUMMARY}} LastUpdated: {{DATE}} WhatFor: > <!-- 2–5 sentences: what outcome does this workflow enforce? --> WhenToUse: > <!-- Trigger conditions: "Use when ..." --> --- # {{TITLE}} ## Overview <!-- 2–5 sentences: why this skill matters and what it enforces --> ## When to Use <!-- concrete triggers + examples -->
documentation58
ttmp/_guidelines
# Guidelines: Skill Documents ## Purpose Skills are **disciplined workflows** written as documents (`DocType: skill`) that teach LLMs (and humans) *how to work*, not just what exists. A good skill turns “best practice” into a repeatable, enforceable process. Skills are meant to be discoverable via: - `docmgr skill list` (filter by topics, file/dir, ticket) - `docmgr skill show <query>` (load and apply a skill) ## Required Elements - **Frontmatter contract** - `DocType: skill` - `Title`: U
development39
ttmp/_templates
--- Title: {{TITLE}} Ticket: {{TICKET}} Status: draft Topics: {{TOPICS}} DocType: skill Intent: long-term Owners: {{OWNERS}} RelatedFiles: [] ExternalSources: [] Summary: > {{SUMMARY}} LastUpdated: {{DATE}} WhatFor: > <!-- 2–5 sentences: what outcome does this workflow enforce? --> WhenToUse: > <!-- Trigger conditions: "Use when ..." --> --- # {{TITLE}} ## Overview <!-- 2–5 sentences: why this skill matters and what it enforces --> ## When to Use <!-- concrete triggers + examples -->
documentation39
ttmp/_templates
--- Title: "Skill: [Name]" Ticket: [TICKET-ID] DocType: skill Status: active Topics: [] WhatFor: "Brief description of what this skill is for" WhenToUse: "Brief description of when to use this skill" RelatedFiles: [] Intent: long-term Owners: [] ExternalSources: [] Summary: "" LastUpdated: [TIMESTAMP] --- # Skill: [Name] ## Overview [Brief overview of the skill] ## What This Skill Is For [Detailed description of what this skill is for] ## When To Use This Skill [Detailed description of wh
documentation13
internal/templates/embedded/_templates
--- Title: {{TITLE}} Ticket: {{TICKET}} Status: draft Topics: {{TOPICS}} DocType: skill Intent: long-term Owners: {{OWNERS}} RelatedFiles: [] ExternalSources: [] Summary: > {{SUMMARY}} LastUpdated: {{DATE}} WhatFor: > <!-- 2–5 sentences: what outcome does this workflow enforce? --> WhenToUse: > <!-- Trigger conditions: "Use when ..." --> --- # {{TITLE}} ## Overview <!-- 2–5 sentences: why this skill matters and what it enforces --> ## When to Use <!-- concrete triggers + examples -->
documentation13
ttmp/_guidelines
# Guidelines: Skill Plans ## Purpose Skills are packaged workflows defined by a `skill.yaml` plan and an exported `SKILL.md` body. The plan tells docmgr what to package (files, help output), while the body teaches LLMs (and humans) *how to work*, not just what exists. Skills are meant to be discoverable via: - `docmgr skill list` (filter by topics, file/dir, ticket) - `docmgr skill show <query>` (load and apply a skill plan) ## Required Elements - **skill.yaml metadata** - `skill.name`: low
documentation13
internal/templates/embedded/_guidelines
# Guidelines: Skill Documents ## Purpose Skills are **disciplined workflows** written as documents (`DocType: skill`) that teach LLMs (and humans) *how to work*, not just what exists. A good skill turns “best practice” into a repeatable, enforceable process. Skills are meant to be discoverable via: - `docmgr skill list` (filter by topics, file/dir, ticket) - `docmgr skill show <query>` (load and apply a skill) ## Required Elements - **Frontmatter contract** - `DocType: skill` - `Title`: U
development13