SKILLEMALL.ai
GitHub ↗ RU Sign in

BB create-agent-issue

Create a single high-quality GitHub issue in logancyang/obsidian-copilot-preview from a TODO item, design-doc punch list entry, or ad-hoc feature/bug request. Each invocation is exactly one issue end-to-end: investigate the surface in src/, draft against the standard, ensure labels exist, push via gh, and (if a source file + line were given) edit that line to point at the new issue. Use when asked to "file an issue for X", "open a ticket", or "convert this TODO to an issue".

logancyang/obsidian-copilot Agent Skills author: logancyang AGPL-3.0 1 file body ≈ 2 618 tokens Open the sourcegithub.com↗ analyzed 7 d ago

Create a single high-quality GitHub issue in logancyang/obsidian-copilot-preview from a TODO item, design-doc punch list entry, or ad-hoc feature/bug request.

As a process B 71/100 · Nearly there — weak spots: result and completion, when it triggers, running it twice

GeneratorObsidianGitHubAI and agentsPersonal productivityData and analyticstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
91/100
safety, quality, tests
Safety 60%
95
Quality 40%
84
Run on models
none yet
Process rating
B
71/100
Nearly there
When it triggers w 12
20
Running it twice w 4
30
Result and completion w 14
40
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 1

    ✓ No critical or high findings

    Medium and low: 1
    • medium Broad scope meta-broad-allowed-tools SKILL.md:1
      Broad tool permissions pre-approved: Bash
      allowed-tools: Bash Read Edit Grep Glob

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 71/100

    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 23 mutating operations with no state check
    • 40Result and completion. Does not say what the result is
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 70Failures and branches. 4 branches
    • 85Steps. 52 steps, 1 vague phrases
    • 100Tools and files. Tools declared in frontmatter
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2618 tokens
    • 100Progress reporting. Reports progress
    • low 11 top-level sections: this looks like several domains in one skill
    • low The response is described with custom markup (11 tags): a typed call is more reliable

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • -5TODO / placeholder text left in the skill
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 2 example trigger phrases
    • +3Description length 479: enough signal without eating the budget
    • +4Structure: 12 headings
    • +3Step-by-step instructions: 52 items
    • +4Has examples (4 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.