CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gofrontai

UX/UI design engine for Biodoia ecosystem. Generates distinctive, production-grade frontend interfaces — mockups as HTML pages or working app pages. Real engine: archetype + wireframe + brand + anti-slop guard. (A seeded Style-RNG for anti-monotony is PLANNED, not yet implemented.) Single designs, variants, FGT-SDK.

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skill/gofrontai/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

38%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 command documentation is genuinely actionable, but the skill is buried under large off-topic sections (agent-conduct rules, trading-risk policy) and duplicated, version-conflicting content, with a dangling reference to a nonexistent file. It needs aggressive trimming and restructuring to function as a skill overview.

Suggestions

Remove or move the ANTI-PATTERN REGISTER and the trading/meme-coin risk sections out of SKILL.md entirely — they are agent-conduct policy, not design-engine instructions, and consume most of the token budget.

Merge the "Manuale d'uso approfondito — gofrontai v3.1" with the earlier "Commands" section into one authoritative, de-duplicated command reference, reconciling the v2.0/v3.1 version conflict.

Create the referenced "references/anti-slop-directives-2026.md" file (or remove the pointer) and move the detailed anti-slop workflow and corpus list into it, keeping only a short summary plus the link in SKILL.md.

DimensionReasoningScore

Conciseness

Roughly half the body is off-topic padding for a design-engine skill: a ~90-line ANTI-PATTERN REGISTER about delivery quality, financial-data honesty, and meme-coin/trading-risk rules, plus a "Manuale d'uso v3.1" that duplicates the earlier command list. The core design content could fit in a third of the space.

1 / 5

Actionability

Commands are concrete and copy-paste ready ("gofrontai wireframe \"brief\"", "go run ./cmd/design-page \"brief\"", "gofrontai compete --name \"readmago\" --fidelity 8.0") and cover common cases, though no build/setup steps for the binary are given and the duplication plus planned-vs-shipped confusion creates minor ambiguity.

4 / 5

Workflow Clarity

The anti-slop section gives a 5-step pre-render sequence with a re-audit loop, but the document as a whole has no coherent end-to-end workflow: commands appear twice in conflicting forms (v2.0 subcommands vs. v3.1 manual), and there is no validation step for the generated output beyond the anti-slop re-audit.

3 / 5

Progressive Disclosure

The body is a monolithic inline document — the anti-pattern register and v3.1 manual clearly belong in separate reference files — and its one clearly-signaled reference, "references/anti-slop-directives-2026.md", does not exist in the bundle (no references/ directory), nor do the other cited files (ANTI_SLOP_REPOS.md, CLAIMS-VERIFICATION.md, DESIGN_COMPONENT_LIBRARY_PLAN.md).

2 / 5

Total

10

/

20

Passed

Description

53%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 gives a clear picture of what the tool does and is reasonably distinct, but it entirely lacks a "when to use" trigger clause and leans on ecosystem-internal jargon that users would not naturally say. Natural trigger phrasing and more concrete action verbs would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for UI/UX design, landing pages, mockups, frontend pages, or design variants for Biodoia/FGT-SDK apps."

Replace jargon-laden pipeline shorthand ("archetype + wireframe + brand + anti-slop guard") with concrete actions users recognize: "Generate single pages, multiple variants, brand identities, and React components from a design brief."

Include natural synonyms and formats (landing page, website, web UI, HTML page, design mockup) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

"Generates distinctive, production-grade frontend interfaces — mockups as HTML pages or working app pages" names the domain and 1-2 concrete actions, but "archetype + wireframe + brand + anti-slop guard" is pipeline jargon rather than user-facing actions and coverage is not comprehensive.

3 / 5

Completeness

The description clearly answers "what" (a frontend design engine producing HTML/app pages) but contains no "when" guidance at all — no "Use when..." clause or equivalent trigger phrasing — which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Some natural keywords are present ("UX/UI design", "frontend interfaces", "mockups", "HTML pages"), but they are diluted by project-internal jargon ("Biodoia ecosystem", "FGT-SDK", "Style-RNG") and common variations or synonyms ("landing page", "website", "web design") are missing.

3 / 5

Distinctiveness Conflict Risk

"UX/UI design engine for Biodoia ecosystem" with FGT-SDK framing carves a mostly distinct niche with minor overlap risk against generic frontend/web-design skills; not 5 because the design/UI triggers don't sharply separate it from those adjacent skills.

4 / 5

Total

13

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

referenced_paths_exist

Referenced path issues: 1 possibly missing (references/anti-slop-directives-2026.md)

Warning

Total

14

/

16

Passed

Repository

biodoia/readmago

Path

skill/gofrontai/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.