CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fossbilling-theme-development

Use when creating, modifying, debugging, or verifying FOSSBilling themes, Twig templates, cart & checkout workflows, ticket and invoice systems, API forms, or strict-mode Twig runtime behavior. Excludes core FOSSBilling PHP backend development or server infrastructure management.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

A high-quality, executable engineering guide packed with FOSSBilling-specific pitfalls and ready-to-use code. Its main gaps are a verification command that references a script missing from the bundle, no explicit validate-fix-retry loop in the verification protocol, and a monolithic body that could offload reference material to bundle files.

Suggestions

Ship the referenced validator (or correct the path) so the verification command `python3 AGENTARDS/scripts/validate_theme.py` is actually executable, since no scripts/ directory exists in the bundle.

Add an explicit feedback loop to Section 6 (e.g., "If static validation or a form life-cycle check fails, fix the template and re-run the check; only declare complete when all three stages pass").

Move the variable cheat sheet (Section 3) and the full theme.js/flash-message implementation (Section 5) into references/ files, keeping SKILL.md as a leaner overview with clearly signaled links.

DimensionReasoningScore

Conciseness

The body is dense with genuinely non-obvious FOSSBilling specifics (silent block drop, the false|default(true) inversion, the native POST 404 pitfall) and avoids explaining generic concepts. Minor redundancy could be trimmed: the CAUTION callout restates the Golden Rule, and the cheat sheet partially repeats the rules from section 3.

4 / 5

Actionability

Mostly executable, copy-paste-ready guidance: a complete layout template, a full form + JS API-submission pattern, and a working flash-message implementation. The gap is that the verification step cites "python3 AGENTARDS/scripts/validate_theme.py", a script that does not exist in the skill's bundle, making that command non-executable as written.

4 / 5

Workflow Clarity

Section 6 provides a clear three-stage verification sequence (static validation, interactive form life-cycle, cross-device visual evidence) with explicit checkpoints such as "Confirm server responses: HTTP 200 OK" and "Confirm redirect destination loads without 404". However, it lacks an explicit feedback loop (if validation fails, fix and re-validate before proceeding) that the top anchor requires.

4 / 5

Progressive Disclosure

Well organized as a single self-contained file with six numbered sections and clear headers, and no buried or nested references. At ~245 lines, some inline content (the variable cheat sheet, the full JS patterns) is a candidate for extraction into references/ files, which keeps this below the top anchor.

4 / 5

Total

16

/

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.

A strong description: it specifies concrete actions, an explicit and detailed "Use when" trigger clause, and clear boundary exclusions. The only weakness is modest synonym coverage (e.g., "client area", ".twig files") that would make triggering marginally more reliable.

DimensionReasoningScore

Specificity

Names four concrete actions ("creating, modifying, debugging, or verifying") across seven specific artifact types ("FOSSBilling themes, Twig templates, cart & checkout workflows, ticket and invoice systems, API forms, or strict-mode Twig runtime behavior"), giving comprehensive coverage of the theming domain with no noticeable gaps.

5 / 5

Completeness

Opens with an explicit "Use when..." clause listing concrete trigger scenarios, and the verb list explicitly states what the skill does; the "Excludes core FOSSBilling PHP backend development or server infrastructure management" clause further sharpens scope. Both what and when are explicit.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("FOSSBilling themes", "Twig templates", "cart & checkout", "ticket", "invoice", "API forms"), but misses common variations a user might naturally say such as "client area", "custom theme", or ".twig" files that a 5-level anchor requires.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (FOSSBilling theming) with distinct triggers, and the explicit exclusion of "core FOSSBilling PHP backend development or server infrastructure management" minimizes overlap with backend or ops skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing, 2 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

administrakt0r/pro-skills-repo-administraktor

Path

skills/UI-UX-skills/fossbilling-theme-development/SKILL.md

Reviewed

Table of Contents

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.