altllm-portal-billing

Use this skill when the user asks to inspect AltLLM Portal balance, redeem a promo code, review billing transactions, or view usage analytics by period, model, or API key using the local altllm CLI. Do NOT use for API key lifecycle management or payment-link execution.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, concise overview that delegates executable detail to a single one-level-deep reference, with clear setup sequencing and a useful command/flag rules section. Adding one or two inline executable examples and a brief output-validation note would round out actionability and workflow clarity.

Suggestions

Inline one or two copy-paste-ready command invocations (e.g., the credit or transactions example) in the body so the core cases are actionable without opening the reference.

Add a brief validation note for state-changing commands like redeem-promo (e.g., re-run credit or check transactions to confirm the promo applied) to strengthen workflow clarity.

Clarify in the command index which usage commands require a date flag vs. default to the current month, so users know when to pass --month or an explicit range without reading the reference.

Dimension	Reasoning	Score
Conciseness	The body is lean and information-dense — a compact command-index table and terse, useful rules (e.g., "transactions supports --page, --limit, and --type") with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Commands and flag semantics are concrete and actionable, but the fully executable invocations (node dist/cli.js ...) live in the reference file rather than inline, leaving a minor gap versus copy-paste-ready guidance.	4 / 5
Workflow Clarity	A clear preflight/setup checkpoint and an unambiguous command-to-purpose mapping make the single-purpose read-only workflow clear; it falls short of 5 only because there is no explicit output-validation guidance (e.g., confirming a promo redemption succeeded).	4 / 5
Progressive Disclosure	The body is a clear overview that points one level deep to a real, verified references/cli-reference.md ("See references/cli-reference.md for filters, examples, and representative outputs"), with well-organized sections and easy navigation.	5 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and distinctive: it enumerates concrete actions, gives explicit trigger guidance with a negative boundary, and is tightly scoped to the AltLLM Portal billing niche. Only minor trigger-term synonym coverage keeps it from a perfect score across every dimension.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete, comprehensive actions — "inspect AltLLM Portal balance, redeem a promo code, review billing transactions, or view usage analytics by period, model, or API key" — matching the score-5 anchor for comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what (inspect/redeem/review/view analytics) and when ("Use this skill when the user asks to...") with concrete trigger phrases, plus a negative boundary clause.	5 / 5
Trigger Term Quality	Good natural keyword coverage ("balance," "promo code," "billing transactions," "usage analytics"), but missing common synonyms like "credits," "invoice," or "spend," so it sits at 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	A clear niche tied to the "AltLLM Portal" / "local altllm CLI" with an explicit "Do NOT use for..." boundary, giving minimal conflict risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: internet-court/internet-court-skill
Path: vendored/altlayer/altllm-portal-billing/SKILL.md
Commit: fa89195

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.