SKILLEMALL.ai
GitHub ↗ RU Sign in

AC gemini-interactions-api

Build with the Gemini Interactions API for text, chat, multimodal generation, streaming, managed or background agents, function calling, structured output, and generateContent migrations.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 2 files body ≈ 4 679 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Build with the Gemini Interactions API for text, chat, multimodal generation, streaming, managed or background agents, function calling, structured output…

As a process C 51/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, running it twice

IntegrationSoftware developmenttype 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
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
89
Run on models
none yet
Process rating
C
51/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills

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 · 0

    ✓ No critical or high findings

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

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "source_repo"
    • note frontmatter-key unknown frontmatter key "source_type"
    • note frontmatter-key unknown frontmatter key "date_added"
    • note frontmatter-key unknown frontmatter key "license_source"
    • note edit-residue the text marks something as outdated (lines 27, 28, 43, 44, 54): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 51/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 9 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 60Tools and files. Uses tools (bash, web, python, node) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70Execution cost. Instruction body is 4679 tokens
    • 85Steps. 80 steps, 1 vague phrases
    • 100Consistency. Name and required fields are in place
    • low 12 top-level sections: this looks like several domains in one skill

    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

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +2Single-language instructions
    • +3Description length 187: enough signal without eating the budget
    • +4Structure: 34 headings
    • +3Step-by-step instructions: 80 items
    • +3Output format is stated explicitly
    • +4Has examples (12 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)
    • +1License stated

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