CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-belgian-search-trinity

Master the "Trinity" of Belgian Search: SEO, AEO, and GEO copy for SMEs to rank on Google and get cited by AI. Use when: Generate location-specific landing pages for all Belgian municipalities; Create FAQ sections structured for verbatim citation by ChatGPT and Claude; Incorporate accurate Flemish/Walloon subsidy data into service pages.

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/nex-belgian-search-trinity/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

28%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 reads as a product landing page rather than a skill instruction file: it markets capabilities ("automates", "provides accurate data", "builds content calendars") without shipping the templates, subsidy data, citation patterns, or any step-by-step procedure needed to execute them, and its own note admits the scripts and templates are not in the folder. Roughly half the tokens are promotional prose and a purchase-oriented FAQ that add no operational value. It needs to be rewritten as instructions: the actual landing-page structure, the verbatim-citation FAQ pattern, the subsidy data (with source and date), and a validation step for figures.

Suggestions

Add a numbered workflow for the core task — e.g. 1. confirm the service and municipality, 2. draft the /{service}-{gemeente} page structure, 3. write the FAQ block using the citation pattern, 4. generate LocalBusiness/FAQPage/Breadcrumb JSON-LD, 5. validate the JSON-LD and verify every subsidy figure against its source before presenting the page.

Replace the marketing prose and the promotional Q&A section with the actual operative content: the verbatim-citation FAQ pattern, the internal-linking structure for the Belgian SME funnel, and the full EUR-formatting/regional-premie rules (or ship them as referenced files like templates/location-page.md and references/subsidies.md).

Move time-sensitive figures such as "maximaal 4.500 EUR in 2026" into a dated reference table with the source (e.g. VEKA) and a required verification step, instead of hardcoding them in an example with no deprecation or dating context.

DimensionReasoningScore

Conciseness

The body is padded with promotional material Claude cannot act on: "Dominate Belgian Search and AI Landscapes", "In the modern search environment, ranking on Google (SEO) is no longer enough", a five-question marketing FAQ ("What exactly is included in the purchase..."), and repeated plugs for nex-ai.be/slopsome.com/agensi.io. It also explains concepts Claude already knows and inlines a time-sensitive figure ("maximaal 4.500 EUR in 2026") with no dated/deprecated framing. This matches anchor 2 (several unnecessary padded sections) rather than 1, since the file is not a wall of text and does contain some usable signal (the example output, the EUR-after-amount rule).

2 / 5

Actionability

Guidance is mostly descriptive rather than instructive: "This skill automates the creation of high-converting... copy", "Provides accurate, up-to-date data on Belgian subsidies" (with no data included), "Scripts, extension source, and templates from the original package are not in this folder". There are only fragments of executable guidance — one worked example output and one micro-rule ("it knows to put 'EUR' after the amount") — with none of the FAQ citation patterns, page templates, or linking structures actually specified. This matches anchor 2 (high-level hints, missing specific steps to execute); anchor 3 would require concrete but incomplete instructions, which are largely absent.

2 / 5

Workflow Clarity

No sequence of steps exists for any of the advertised outputs — nothing on how to research a municipality, structure the landing page, draft the FAQ block, assemble the JSON-LD, or verify subsidy figures, and no validation checkpoints despite the body itself admitting "Requires manual verification of real-time subsidy (premie) changes". A rough output shape is only implied by the example (H1 → FAQ → JSON-LD), which keeps this at anchor 2 rather than dropping to 1 (steps missing entirely with no discernible shape).

2 / 5

Progressive Disclosure

The body has reasonable section structure (What it does / When to use / Known limitations / Example) with no nested references, but the material that clearly belongs in separate files — the subsidy data tables, page templates, and FAQ citation patterns the body promises — is simply absent rather than referenced (only promotional external URLs are linked), and the marketing Q&A section is misplaced content for a skill file. This fits anchor 3 (some structure, could be better organized); it is above 2 because nothing is inlined that should be split out, and below 4 because the promised detailed materials have no clear, signaled home.

3 / 5

Total

9

/

20

Passed

Description

87%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: concrete capability statements paired with an explicit, multi-trigger "Use when" clause and a sharply distinct Belgian-market niche. Its only weaknesses are mild marketing padding ("Master the 'Trinity'") and jargon abbreviations (AEO, GEO) that some users would not naturally say, plus omission of the schema/calendar capabilities the body claims.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Generate location-specific landing pages for all Belgian municipalities", "Create FAQ sections structured for verbatim citation by ChatGPT and Claude", "Incorporate accurate Flemish/Walloon subsidy data into service pages" — but omits capabilities the body advertises (Schema.org JSON-LD, content calendars) and pads with marketing phrasing ("Master the 'Trinity'"). This matches anchor 4 (several specific actions, minor coverage gaps) rather than 5 (comprehensive) or 3 (only 1-2 actions).

4 / 5

Completeness

It explicitly answers both questions: the "what" is "SEO, AEO, and GEO copy for SMEs to rank on Google and get cited by AI", and the "when" is an explicit "Use when:" clause with three concrete trigger phrases. This matches the anchor-5 example structure (capabilities followed by explicit triggers); score 4 would require the "when" to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "SEO", "landing pages", "FAQ", "ChatGPT and Claude", "Belgian municipalities", "Flemish/Walloon subsidy" are phrases a user needing this skill would plausibly say. A few natural terms are missing ("local SEO", "near me", specific city names, "premie", "rank"), and "AEO"/"GEO" are insider jargon most users would not say — anchor 4, not 5 (no full synonym coverage) and clearly above 3 (which would miss common variations).

4 / 5

Distinctiveness Conflict Risk

The niche is unusually clear — Belgian-market-specific copy, Flemish/Walloon subsidies, Belgian municipalities — with triggers that would not fire for generic SEO or general copywriting skills. Minimal conflict risk, matching anchor 5; anchor 4 would imply overlap with closely related skills, which the heavy geographic/regional anchoring avoids.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

NexaiGuy/nex-ai-skills

Path

skills/nex-belgian-search-trinity/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.