Skip to content

chore: add concrete patterns, remove mandatory skill invocation #9

@CybotTM

Description

@CybotTM

Quality Review Finding

Per marketplace tracking issue, this skill has critical quality issues:

Word count: 300 (but 95% are reference pointers)

Issues

  1. No actual pattern content — skill is 95% pointers to reference files, with almost no concrete patterns in the body
  2. Invalid "Required Workflow" mandate — "For comprehensive reviews, ALWAYS invoke these related skills" violates skill independence principle. A skill should work standalone; invoking other skills is the agent's decision
  3. Empty "Quick Reference" — headings like "Type Safety: Avoid interface{}" without examples
  4. Weak description — "Production-grade Go development patterns" is vague

Recommended Actions

  • Remove "Required Workflow" section entirely
  • Add 2-3 concrete pattern examples directly in the skill (not hidden in references)
  • Add "Quick Reference" with annotated code snippets showing core principles
  • Rewrite description: "Use when implementing Go services, designing resilient systems, setting up test suites, or optimizing performance."

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions