SKILLEMALL.ai
GitHub ↗ RU Sign in

AC Analyze Creator Financial Health with Automated Reporting

Analyze creator revenue streams (Stripe, PayPal, affiliate, sponsorships) to calculate true profitability per content piece, identify unprofitable segments, forecast cash flow gaps, and recommend high-margin content verticals. Use when the user needs revenue analysis, margin reporting, content ROI, or cash flow forecasting.

ClawHub Agent Skills author: ncreighton v1.0.0 MIT-0 2 files body ≈ 3 495 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

Analyze creator revenue streams (Stripe, PayPal, affiliate, sponsorships) to calculate true profitability per content piece, identify unprofitable segments…

As a process C 60/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, consistency

AnalyzerStripeData and analyticsFinancetype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
81
Run on models
none yet
Process rating
C
60/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

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

    • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
    • note frontmatter-key unknown frontmatter key "homepage"

    Process rating: all ten parameters 60/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. 7 mutating operations with no state check
    • 40Consistency. Frontmatter name (Analyze Creator Financial Health with Automated Reporting) differs from the folder (creator-financial-health-auditor)
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. No external tools needed
    • 100Steps. 44 steps
    • 100Execution cost. Instruction body is 3495 tokens

    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)
    • +1No license
    • +2Single-language instructions
    • +3Description length 325: enough signal without eating the budget
    • +4Structure: 25 headings
    • +3Step-by-step instructions: 44 items
    • +3Output format is stated explicitly
    • +4Has examples (18 code blocks)

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

    External checks

    ClawHub: suspicious
    The skill is coherent for financial reporting, but it asks for live payment and business-service credentials without enough scoping or secret-handling guidance.
    LLM: suspicious (high) · 21 Aug 2026