SKILLEMALL.ai
GitHub ↗ RU Sign in

AC linkedin-analytics

Use when someone wants to understand their own LinkedIn numbers — which posts worked, why reach dropped, whether a pattern is real, or how to test a hypothesis. Triggers on "why did my reach drop", "what's working on my LinkedIn", "analyze my posts", "do carousels do better for me", "should I test this", "LinkedIn analytics". Reads your own exported post data, reports medians and outlier bands, tests candidate patterns against a permutation null, and sizes a real experiment — refusing to conclude anything below 10 posts.

alirezarezvani/claude-skills Agent Skills author: alirezarezvani MIT 8 files body ≈ 1 159 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Triggers on "why did my reach drop", "what's working on my LinkedIn", "analyze my posts", "do carousels do better for me", "should I test this", "LinkedIn…

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

ProcedureData 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
A
99/100
safety, quality, tests
Safety 60%
100
Quality 40%
97
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
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: 8. 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 51/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 30Running it twice. 1 mutating operations with no state check
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 100Steps. 13 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1159 tokens
    • 100Progress reporting. Reports progress

    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
    • +2Single-language instructions
    • +5Description quotes 6 example trigger phrases
    • +3Description length 526: enough signal without eating the budget
    • +4Structure: 6 headings
    • +3Step-by-step instructions: 13 items
    • +4Has examples (3 code blocks)
    • +4Reference files are cited in the instructions (2 of 2)
    • +3All 3 scripts are documented
    • +1License stated

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