SKILLEMALL.ai
GitHub ↗ RU Sign in

AA sales-engineer

Technical sales engineering: demos, solution design, RFP responses, and POC management. Use when preparing demos, responding to RFPs/RFIs, scoping proof-of-concepts, building battle cards, or handling technical objections.

borghei/Claude-Skills Agent Skills author: borghei 4 files · 3 scripts body ≈ 3 849 tokens Open the sourcegithub.com↗ analyzed 8 h ago

Technical sales engineering: demos, solution design, RFP responses, and POC management.

As a process A 80/100 · Runs to the end — weak spots: inputs and preconditions, running it twice

ProcedureProcurementtype 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%
91
Run on models
none yet
Process rating
A
80/100
Runs to the end
Inputs and preconditions w 11
0
Running it twice w 4
30
When it triggers w 12
50
the three weakest of ten parameters · all ten

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: 4. 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 80/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 4 mutating operations with no state check
    • 50When it triggers. No condition that starts the skill
    • 100Tools and files. No external tools needed
    • 100Steps. 39 steps
    • 100Result and completion. Output format and completion criterion are stated
    • 100Failures and branches. 1 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3849 tokens
    • 100Progress reporting. Reports progress
    • low 13 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 222: enough signal without eating the budget
    • +4Structure: 21 headings
    • +3Step-by-step instructions: 39 items
    • +3Output format is stated explicitly
    • +4Has examples (6 code blocks)
    • +3All 3 scripts are documented
    • +1License stated

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