Skill Creator

GolferGeek

13 published skills · 0 GitHub stars across the catalog. View on GitHub ↗

api-agent-development

GolferGeek's avatarfrom GolferGeek

Create API agents that wrap external HTTP services (n8n, LangGraph, CrewAI, OpenAI endpoints). Configure request/response transforms, webhook status tracking, A2A protocol compliance. CRITICAL: Request transforms use template variables ({{userMessage}}, {{conversationId}}, etc.). Response transforms use field extraction. Status webhook URL must read from environment variables.

back-end-structure

GolferGeek's avatarfrom GolferGeek

Build NestJS backend following Orchestrator AI patterns. Module/Service/Controller structure, A2A protocol compliance, transport types, error handling. CRITICAL: Files follow kebab-case naming. Controllers handle HTTP, Services contain business logic, Modules organize dependencies.

conventional-commits

GolferGeek's avatarfrom GolferGeek

Conventional Commits specification format. Use when creating commit messages. Format: <type>(<scope>): <description>. Types: feat, fix, chore, docs, test, refactor, style, perf. CRITICAL: All commits must follow conventional commit format.

crewai-development

GolferGeek's avatarfrom GolferGeek

Create CrewAI workflows as NestJS applications under apps/crewai/. FUTURE: Same pattern as LangGraph - NestJS app, same webhook pattern as n8n, receive same parameters, wrap as API agents. CRITICAL: Status webhook URL must read from environment variables.

front-end-structure

GolferGeek's avatarfrom GolferGeek

Build Vue 3 + Ionic front-end components following Orchestrator AI's strict architecture: stores hold state only, services handle API calls with transport types, components use services and read stores. CRITICAL: Maintain view reactivity by keeping stores simple - no methods, no API calls, no business logic.

github-workflow

GolferGeek's avatarfrom GolferGeek

GitHub workflow patterns for Orchestrator AI. Branch naming, PR process, code review, CI/CD. CRITICAL: Use conventional branch names (feature/, fix/, chore/). PRs require quality gates to pass. Use GitHub Actions for CI/CD.

langgraph-development

GolferGeek's avatarfrom GolferGeek

Create LangGraph workflows as NestJS applications under apps/langgraph/. Use same webhook pattern as n8n, receive same parameters (taskId, conversationId, userId, provider, model, statusWebhook). Wrap as API agents with request/response transforms. CRITICAL: Status webhook URL must read from environment variables. All endpoints follow A2A protocol.

create-new-skills

GolferGeek's avatarfrom GolferGeek

Creates new Agent Skills for Claude Code following best practices and documentation. Use when the user wants to create a new skill, extend Claude's capabilities, or package domain expertise into a reusable skill.

n8n-development

GolferGeek's avatarfrom GolferGeek

Create and manage N8N workflows in Orchestrator AI. Use Helper LLM pattern for all LLM calls, configure webhook status tracking, handle API responses. CRITICAL: All workflows using Helper LLM must include required parameters (taskId, conversationId, userId, statusWebhook, stepName, sequence, totalSteps). Status webhook URL must read from environment variables.

orchestrator-git-standards

GolferGeek's avatarfrom GolferGeek

Orchestrator AI-specific Git conventions and standards. Branch naming, commit workflow, repository organization. CRITICAL: Follow conventional branch names, use conventional commits, maintain clean git history.

quality-gates

GolferGeek's avatarfrom GolferGeek

Ensure code quality before commits. Run lint, format, test, build. Use npm scripts: npm run lint, npm run format, npm test, npm run build. CRITICAL: All tests must pass, no lint errors, code must be formatted before committing.

supabase-management

GolferGeek's avatarfrom GolferGeek

Manage Supabase database using Orchestrator AI's storage-based sync system. Use when working with Supabase, database snapshots, migrations, agent exports, N8N workflow exports, backups, or storage scripts. CRITICAL: Prevents direct Supabase operations - all operations MUST use storage/scripts/*.sh

worktree-lifecycle

GolferGeek's avatarfrom GolferGeek

Manage git worktree lifecycle for parallel development. Create worktrees with port isolation, manage multiple branches simultaneously, clean up worktrees. CRITICAL: Use /create_worktree command, never manual git worktree commands. Ports auto-calculated to avoid conflicts.