← all publishers

cobusgreyling

@cobusgreyling source repo

Report this profile Claim this profile

• 45 skills
• 0 followers
• 6 hours ago last updated

1. ▌
   CI Triage · cobusgreyling

   Parse CI failures, identify failing job/step, classify as flake, regression, env, or config. Use in CI sweeper loops before any fix attempt.
   0
   installs
2. ▌
   Issue Triage · cobusgreyling

   Scan open issues and discussions. Dedupe, prioritize, and propose labels. Updates issue-triage-state.md. L1 propose-only — never auto-label or close.
   0
   installs
3. ▌
   Goal Verifier 2 · cobusgreyling

   Independently verify a Grok Build goal is truly complete. Checks GOAL.md done conditions, runs tests, and returns PASS or REJECT. Use before update_goal(completed: true).
   0
   installs
4. ▌
   Goal Verifier 3 · cobusgreyling

   Verify migrate-module goals: tests green, zero legacy imports, GOAL.md checklist complete. Use before update_goal(completed: true) on module migration goals.
   0
   installs
5. ▌
   Goal Verifier 4 · cobusgreyling

   Verify coverage-target goals: coverage threshold met, no hollow tests, suite green. Use before update_goal(completed: true) on coverage goals.
   0
   installs
6. ▌
   Goal Verifier 5 · cobusgreyling

   Verify refactor-safely goals: full test lock, no public API breakage, behavior preserved. Use before update_goal(completed: true) on refactor goals.
   0
   installs
7. ▌
   Goal Verifier 6 · cobusgreyling

   Verify implement-feature goals: acceptance criteria met, tests for new behavior, checklist complete. Use before update_goal(completed: true) on feature goals.
   0
   installs
8. ▌
   Skill Crafter · cobusgreyling

   Create high-quality, production-ready Grok Build skills (SKILL.md files). Generates correct YAML frontmatter (name, description with specific triggers, when-to-use, argument-hint), clear numbered steps, tool references, and principles. Use when the user says "create a skill", "write a skill for...", "gbs scaffold skill", "/create-skill", "/skillify", or when implementing the scaffold command for skills.
   0
   installs
9. ▌
   Project Auditor · cobusgreyling

   Perform a thorough Grok Build readiness audit on a project directory. Detects presence and quality of AGENTS.md, .grok/skills, test setup, CI configuration, git hygiene, and ignore files. Produces a 0-100 score plus actionable recommendations. Use when asked to "audit", "gbs audit", "check grok readiness", "is this project agent-friendly", "grok build readiness", or when building/using the gbs audit command.
   0
   installs
10. ▌
    Readiness Scorer · cobusgreyling

    Calculate and explain a "Grok Readiness Score" (0-100) for a project based on concrete signals: quality of AGENTS.md / project rules, quantity and validity of skills, test/CI presence, git hygiene, ignore configuration, and verification culture. Use when asked to "score", "readiness score", "grok score", "how agent friendly is this", or as part of an audit workflow or the gbs audit implementation.
    0
    installs
11. ▌
    Git Discipline · cobusgreyling

    Enforce conventional commits, clean branch strategy, small focused diffs, and PR-ready history. Use before any commit or when preparing work for review. Triggers: "commit this cleanly", "prepare for PR", "fix the git history", "use git-discipline".
    0
    installs
12. ▌
    Security Audit · cobusgreyling

    Perform focused security reviews on code, diffs, hooks, and MCP servers. Look for auth issues, injection, secret leakage, unsafe tool/MCP usage, and hook risks. Use for any change involving external input, credentials, or agent capabilities. Triggers: "security review", "audit this diff", "check for vulnerabilities".
    0
    installs
13. ▌
    Subagent Arena · cobusgreyling

    Run parallel independent subagents on the same investigation or design question, collect structured outputs, then synthesize the best elements or score approaches. Use for complex research, architecture decisions, or when multiple valid strategies exist. Trigger with "run an arena", "parallel subagents", "compare approaches", "investigate from multiple angles".
    0
    installs
14. ▌
    MCP Orchestrator · cobusgreyling

    Discover available MCP servers, evaluate their fit, install and configure them safely, and then use them effectively within sessions. Use when the user needs new capabilities (browser control, advanced git, observability, etc.) or when existing MCPs are under-utilized. Triggers: "set up MCPs", "install the right tools", "add an MCP for...", "what MCPs do we need?"
    0
    installs
15. ▌
    Tdd Intelligence · cobusgreyling

    Apply rigorous test-first development. Write failing tests (or characterization tests) that capture desired behavior before implementing. Maintain high test coverage on changed code. Use for new features, refactors, and bug fixes where regression protection matters. Triggers: "TDD this", "test first", "write the test then implement", "add characterization tests".
    0
    installs
16. ▌
    Architecture Reviewer · cobusgreyling

    Perform focused architecture and modularity reviews. Identify boundary violations, god objects, tangled dependencies, and propose the smallest reversible improvements. Use the repo-graph MCP when available. Trigger with "architecture review", "check the boundaries", "is this modular enough?".
    0
    installs
17. ▌
    Plan Mode Orchestrator · cobusgreyling

    For any non-trivial task, start in Plan Mode, produce a clear step-by-step plan with risks and verification method, and wait for explicit approval before any edits. Use when the user says "plan this", "use plan mode", "don't edit yet", or describes a complex feature/refactor/migration.
    0
    installs
18. ▌
    Goal Scoper · cobusgreyling

    Break a large request into a bounded, goal-ready objective with verifiable done conditions. Use before /goal when the task is vague, too large, or missing acceptance criteria. Produces GOAL.md draft content.
    0
    installs
19. ▌
    Goal Verifier · cobusgreyling

    Independently verify a Grok Build goal is truly complete. Checks GOAL.md done conditions, runs tests, and returns PASS or REJECT with evidence. Use before update_goal(completed: true), when asked to "verify goal", "check if done", or as a reviewer sub-agent at the end of a goal run.
    0
    installs
20. ▌
    Goal Completion Check · cobusgreyling

    Pre-flight check before calling update_goal(completed: true). Ensures verifier ran, tests passed, and GOAL.md checklist is complete. Use when implementer believes work is done, or when asked "can I mark goal complete?"
    0
    installs
21. ▌
    LLM As Judge · cobusgreyling bundle

    Design and validate LLM-as-judge scoring — pairwise vs pointwise, bias correction, anchor calibration, and the cases where a judge is the wrong tool. Use when the user is building an eval, scoring open-ended outputs, or comparing model versions and mentions LLM-as-judge, model grader, pairwise comparison, position bias, length bias, judge calibration, meta-eval, or asks "how do I score open-ended responses?" / "is my LLM-judge biased?".
    0
    installs
22. ▌
    Memory Design · cobusgreyling bundle

    Design memory for an LLM agent — what to keep, where to keep it, and when memory hurts more than it helps. Use when the user is adding memory to an agent and mentions short-term memory, long-term memory, episodic, semantic, conversation history, summary memory, vector memory, memory store, mem0, Letta, MemGPT, or asks "should this agent remember?" / "why is the agent recalling the wrong thing?".
    0
    installs
23. ▌
    Model Routing · cobusgreyling bundle

    Pick the right model per call, not per project — route Opus/Sonnet/Haiku, GPT-5/4o/mini, Gemini Pro/Flash by task, and cut cost without losing quality. Use when the user is choosing model tiers, building a router, or debating Opus-only vs mixed-tier deployments and mentions model selection, model router, cascade, fallback, cheap-first, draft-then-verify, or asks "which model should I use?" / "do I need Opus for this?".
    0
    installs
24. ▌
    Prompt Caching · cobusgreyling bundle

    Use prompt caching correctly across Anthropic, OpenAI, Bedrock, and Gemini to cut cost and latency on hot paths. Use when the user is building a production LLM app and mentions prompt caching, cache hits, cache key, cache TTL, ephemeral cache, system-prompt caching, or asks "why is my cache hit rate low?" / "should I cache this?".
    0
    installs
25. ▌
    Human In The Loop · cobusgreyling bundle

    Design where, when, and how a human gates, reviews, or rescues an LLM agent — without turning the agent into a button labelled "approve". Use when the user is building an agent that takes irreversible actions or operates in regulated workflows and mentions human-in-the-loop, HITL, approval gate, escalation, review queue, oversight, or asks "when should a human approve this?" / "how do I add review without killing the agent's speed?".
    0
    installs
26. ▌
    Latency Budgeting · cobusgreyling bundle

    Budget and engineer latency for an LLM agent — TTFT, tokens-per-second, tool round-trips, parallelism, streaming. Use when the user is building a user-facing or real-time agent and mentions latency, p50, p95, p99, TTFT, streaming, throughput, time-to-first-token, slow agent, or asks "why is my agent slow?" / "how do I hit a 2-second latency target?".
    0
    installs
27. ▌
    Agent Cost Modeling · cobusgreyling bundle

    Model the cost of an LLM agent before it ships, and after. Use when the user is planning a deployment, comparing patterns, choosing a model tier, or justifying a budget and mentions tokens per task, cost per task, unit economics, cost ceiling, cache hit rate, ReAct cost, multi-agent cost, or asks "how much will this cost?" / "is this economical at scale?".
    0
    installs
28. ▌
    Agent Observability · cobusgreyling bundle

    Instrument an LLM agent so failures are diagnosable, traces are replayable, and evals can run against production data. Use when the user is moving an agent past prototype and mentions tracing, spans, OpenTelemetry, LangSmith, Langfuse, Arize, OpenLLMetry, structured logs, GenAI semantic conventions, or asks "how do I debug this agent in production?" / "what should I log?".
    0
    installs
29. ▌
    Guardrails And Safety · cobusgreyling bundle

    Design guardrails for an LLM agent that handles user input, calls real tools, or operates in a regulated domain. Use when the user is building a user-facing agent and mentions guardrails, jailbreaks, prompt injection, content moderation, PII redaction, output validation, red-teaming, safety filters, or asks "how do I keep this agent from doing X?" / "how do I make this production-safe?".
    0
    installs
30. ▌
    Tool Failure Handling · cobusgreyling bundle

    Design retry, idempotency, timeout, and recovery behaviour for an agent's tool calls — not the schema (that's a separate skill), but the runtime semantics. Use when the user is building or debugging an agent's tool loop and mentions retries, idempotency keys, timeouts, exponential backoff, compensation, partial failure, tool unavailable, 429, 503, flaky tool, or asks "how should the agent retry?" / "the tool failed mid-call, now what?".
    0
    installs
31. ▌
    Context Window Hygiene · cobusgreyling bundle

    Manage what enters and stays in the context window — pruning, compaction, summary fidelity, ordering — so the agent stays coherent on long runs without inflating cost. Use when the user is hitting context limits, running long agentic loops, paying for full-history replays, or asks "how do I keep context manageable?" / "the agent forgets things after N turns".
    0
    installs
32. ▌
    Tool Use Schema Design · cobusgreyling bundle

    Design tool schemas (function-calling definitions) that LLMs can use reliably. Use when the user is defining tools for Claude, GPT, Gemini, or any function-calling agent and mentions tool definitions, function calling, JSON schema, tool descriptions, parameters, structured outputs, MCP tools, or asks "why is the model calling my tool wrong?" / "how should I design this tool?".
    0
    installs
33. ▌
    Agent Evaluation Harness · cobusgreyling bundle

    Design an evaluation harness for an LLM agent before shipping it. Use when the user is building or rewriting an agent, deciding ship/no-ship, debugging regressions, or mentions golden sets, eval suites, regression tests, trace-level evals, LLM-as-judge, scoring rubrics, or asks "how do I test this agent?" / "how do I know if my agent got better?".
    0
    installs
34. ▌
    Prompt Injection Defense · cobusgreyling bundle

    Defend an LLM agent against prompt injection — direct, indirect, tool-result, and document-borne. Use when the user is building an agent that reads untrusted content (web pages, emails, documents, tool outputs) or exposes user-provided text to a downstream agent, and mentions prompt injection, indirect injection, jailbreak via document, tool-result injection, untrusted input, instruction override, or asks "how do I stop the agent from following injected instructions?" / "is RAG safe from injection?".
    0
    installs
35. ▌
    Multi Agent Orchestration · cobusgreyling bundle

    Decide when to split work across multiple agents vs one agent with tools, and design the handoffs when you do. Use when the user is sketching a multi-agent system or debugging one, and mentions handoff, delegation, supervisor, swarm, crew, sub-agent, agent-to-agent, A2A, manager-worker, team of agents, or asks "should I split this into multiple agents?" / "why do my agents talk forever and never finish?".
    0
    installs
36. ▌
    RAG Vs Context Engineering · cobusgreyling bundle

    Decide between RAG, long-context, structured tool retrieval, and prompt-only approaches for grounding an LLM in private or fresh data. Use when the user is designing a knowledge-grounded agent or chatbot and mentions RAG, vector search, embeddings, retrieval, chunking, long context, context window, tool retrieval, hybrid search, rerank, or asks "do I need RAG?" / "should I just use a big context window?".
    0
    installs
37. ▌
    Agent Architecture Patterns · cobusgreyling bundle

    Choose the right architecture for an LLM agent or multi-agent system. Use when the user is designing, comparing, or debugging agentic workflows and mentions ReAct, Reflexion, Plan-and-Execute, Router, Supervisor, Hierarchical, multi-agent, tool-use loop, agent graph, LangGraph, AutoGen, CrewAI, or asks "which agent pattern should I use" / "how should this agent be structured".
    0
    installs
38. ▌
    Structured Output Reliability · cobusgreyling bundle

    Get reliable structured output (JSON, typed objects) out of an LLM without regex repair, retry loops, or silent corruption. Use when the user is parsing model output, fighting malformed JSON, comparing JSON mode vs function calling vs structured outputs, or asks "why does the model keep breaking my schema?" / "how do I force valid JSON?".
    0
    installs
39. ▌
    Budget Negotiator · cobusgreyling

    An advanced skill for L3 autonomous loops. When the token budget nears exhaustion, the agent analyzes its ROI and autonomously drafts a negotiation request for a budget increase rather than silently failing.
    1
    install
40. ▌
    Loop Constraints · cobusgreyling

    Read loop-constraints.md at the start of every run and enforce every rule. This skill runs BEFORE triage or any action skill. Constraints are binding.
    1
    install
41. ▌
    Loop Verifier · cobusgreyling

    Independent verification agent for loop-produced changes. Finds reasons to reject. Runs tests. Confirms diff scope. Use after minimal-fix or any implementer sub-agent — never in the same role as the implementer.
    1
    install
42. ▌
    Install Loop · cobusgreyling

    Install Loop Engineering into a project via the unified CLI front door (@cobusgreyling/loop). Prefer this over invoking loop-init / loop-audit separately. Week-one is report-only; never enable auto-merge or unattended fixes unless the human explicitly asks and doctor is healthy.
    1
    install
43. ▌
    Loop Budget · cobusgreyling

    Check token budget and run-log spend before and after a loop run. Enforces early exit when over budget or when there is no actionable work.
    1
    install
44. ▌
    Loop Triage · cobusgreyling

    Triage recent changes, CI failures, issues, and conversations. Produces a concise, actionable findings report suitable for a loop to consume. Writes structured output to a state file or Linear board.
    1
    install
45. ▌
    Minimal Fix · cobusgreyling

    Produce the smallest possible code change that fixes a specific, well-scoped issue (CI failure, reviewer comment, typo). Use only when the fix target is explicit. Never refactor unrelated code.
    1
    install