ask

Use when the user asks a question to be answered from the project's memex (long-term knowledge bank for AI agents) rather than training data or the live web. Reads the index, opens relevant pages, follows one SALP-REF hop, synthesises a cited answer, files it back. Do NOT trigger on source-code or live-session questions.

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.

A well-structured, highly actionable workflow skill with concrete templates and sensible error-handling checkpoints. The main improvement room is in conciseness (light redundancy in citation-format restatement) and adding a post-file verification step to push workflow clarity to the top anchor.

Suggestions

Consolidate the SALP REF syntax explanation so the citation format is stated once and referenced, rather than restated across the Resolution, Ask Steps, and Constraints sections.

Add an explicit verify step after filing the answer (e.g., re-read the written file to confirm frontmatter and Sources section are well-formed) to reach the top workflow_clarity anchor.

Tighten the Format guidance and Quality rules bullets, which overlap slightly with the example body shown in step 4.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of generic-knowledge padding; the SALP syntax, resolution rules, and templates are domain-specific and earn their place, though the citation format is restated a few times and a few lines could be trimmed.	4 / 5
Actionability	Fully executable guidance: concrete file paths, copy-paste frontmatter YAML, a slug-derivation rule, an example answer body, and exact log.md/promotion templates cover the common cases.	5 / 5
Workflow Clarity	An explicit 8-step sequence with real checkpoints (honest-gaps check after step 3, missing-index fallback, slug-collision handling), but no verify loop after filing or before promotion, leaving minor validation gaps.	4 / 5
Progressive Disclosure	Clean single-file structure with well-labeled H2/H3 sections, no nested references, and no orphaned bulk content that belongs in a separate file; navigation is straightforward and the self-contained layout is appropriate for this workflow skill.	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.

A strong description that names concrete actions, gives an explicit trigger and a negative boundary, and occupies a clear niche. The only soft spot is trigger-term coverage, which relies on a single term ('memex') without synonym variations.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions covering the full pipeline — 'Reads the index, opens relevant pages, follows one SALP-REF hop, synthesises a cited answer, files it back' — which is comprehensive coverage rather than just naming the domain.	5 / 5
Completeness	Explicitly answers both — 'Use when the user asks a question to be answered from the project's memex' gives the when with a concrete trigger phrase, and the action list gives the what — and adds an explicit anti-trigger.	5 / 5
Trigger Term Quality	Good keyword coverage with natural terms like 'asks a question', 'memex', and 'knowledge bank', plus a negative boundary; missing some common synonyms or phrasings a user might actually say (e.g. 'look this up in my memex' appears only in the body, not the description).	4 / 5
Distinctiveness Conflict Risk	Clear niche (memex-only knowledge lookup) with distinct triggers and an explicit 'Do NOT trigger on source-code or live-session questions' boundary, minimizing conflict with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: korchasa/flowai-plugins
Path: plugins/flowai-memex/skills/ask/SKILL.md
Commit: b4ba256

Reviewed: ~21 hours 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.