CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gofainder

Multi-engine search agent for Biodoia ecosystem. 15+ search engines, crypto price feeds, content extraction, research pipelines. Single binary with subcommands: serve, search, price-feed, chat, mcp, tui, web.

Quality

61%

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/gofainder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 operational core is genuinely actionable — concrete commands, endpoints, and tables — but it is buried in a file where half the content is an unrelated off-topic register, with no validation steps in its workflows and everything inlined in a single monolithic SKILL.md. Splitting the file and excising the register would raise every dimension at once.

Suggestions

Remove the ANTI-PATTERN REGISTER (and the meme-coin/high-risk-mission rules) from this skill file — it is generic agent behavior policy, not gofainder operating instructions; if it must live somewhere, put it in its own skill or reference file.

Move the full command manual, engine table, and provider table into a references/ file (e.g. references/commands.md) and keep SKILL.md as a lean overview with one-level-deep pointers.

Add validation checkpoints to the workflows, e.g. 'gofainder engines' to verify keys before search, and a curl against 127.0.0.1:8086/api/search to confirm serve is running with PORT=8086 set.

DimensionReasoningScore

Conciseness

Roughly half the body (the ~100-line 'ANTI-PATTERN REGISTER' plus the golden-rule and trading-risk sections) is generic behavioral guidance unrelated to operating gofainder — much of it re-explains practices Claude already knows (write tests, handle errors, don't push prematurely). Not a 1 because the operational half (commands, tables, endpoints) is lean and table-driven; clearly below the midpoint though.

2 / 5

Actionability

Concrete executable material throughout the operational sections: build commands ('go build -o gofainder ./cmd/gofainder'), exact endpoints ('GET :8086/api/search?q={query}'), systemd commands, and a per-engine key-requirements table. Not a 5 because some entries are catalog-like (module table, integration list) without runnable examples, and the PORT=8086 workaround is stated twice rather than once with a command.

4 / 5

Workflow Clarity

The harvesting workflow ('research → scrape/extract → biblaigo index → godocai kb-search') and the Rules section give sequences, but there are no validation checkpoints or feedback loops anywhere (e.g., how to verify serve is up before hitting the API, or how to check engine status after configuring keys). Fits 'sequence present but checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

Section headers exist and no bundle files are used, but large content that clearly belongs in separate reference files is inlined: the full command manual ('Manuale d'uso approfondito'), the anti-pattern register, and the engine/provider tables all sit in SKILL.md. Fits 'some structure but could be better organized; content that should be separate is inline'; not a 2 because headers do make the file navigable.

3 / 5

Total

12

/

20

Passed

Description

55%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 concrete, well-scoped 'what' but entirely omits 'when to use it', and its trigger vocabulary is generic enough to risk overlap with other search/crypto skills. Adding an explicit 'Use when...' clause with natural synonyms would lift the two weakest dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to search the web across engines, fetch crypto/token prices, or run research pipelines in the Biodoia ecosystem.'

Include natural synonyms users would actually say (web search, token prices, bitcoin, scrape/extract a URL) to broaden trigger-term coverage.

Trim the subcommand list or pair each with a two-word purpose so the description reads as capabilities rather than a bare command inventory.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities ("15+ search engines", "crypto price feeds", "content extraction", "research pipelines") and concrete subcommands ("serve, search, price-feed, chat, mcp, tui, web"), but stops short of comprehensive coverage of what each does. Not a 5 because coverage has minor gaps; not a 3 because it goes well beyond 1-2 actions.

4 / 5

Completeness

The 'what' is clear (multi-engine search agent with named subcommands), but there is no 'Use when...' clause or any explicit trigger guidance, which caps completeness at 3 per the rubric guidelines. Not a 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

"search", "crypto price feeds", and "content extraction" are natural terms, but coverage is sparse and generic — missing common variations like "web search", "token/bitcoin prices", "scrape", or any file/service extensions. Fits 'some relevant keywords but missing common variations or synonyms' rather than the good-coverage anchor at 4.

3 / 5

Distinctiveness Conflict Risk

Anchoring to "Biodoia ecosystem" and a specific binary gives it a niche, but the actual trigger words ("search", "crypto", "prices", "research") are broad and would overlap with generic search or crypto skills. Fits 'somewhat specific but could still overlap with similar skills'; not a 4 since the common trigger terms are not distinctive.

3 / 5

Total

13

/

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

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository

biodoia/readmago

Path

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