fnl-ask
Skill4 starsChanged 14 days agoMITView on GitHub
Get oriented in finolabs-vibecode: first steps for someone new, what the plugin contains, how a given skill, agent or script works, or which skill fits your situation and the command to type next. Run only when the user asks for it.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- finolabs/vibecodetheir own version, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- finolabs/vibecode★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- rules/AGENTS.mdAGENTS.md
- skills/fnl-delegate/references/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- fnl-advisorSkill
- fnl-coding-routerSkill
- fnl-commit-messagesSkill
- fnl-delegateSkill
- fnl-handoffSkill
- fnl-open-source-reviewSkill
- fnl-plugin-packagingSkill
- fnl-restore-pointSkill
- fnl-review-gateSkill
- fnl-security-review-gateSkill
- fnl-session-hygieneSkill
- fnl-setupSkill
- fnl-statusSkill
- fnl-updateSkill
- fnl-verificationSkill
- fnl-versioningSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Read references/plain-language.md first to decide whether to use the beginner register in any mode, including how to handle a bare …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Ask: where do I start, what is here, which skill next?
Read references/plain-language.md first to decide whether to use the beginner register in any mode, including how to handle a bare invocation. Then pick the mode that fits the user's question and read its reference:
Advisory (agent judgment): Talk to the user in the language they are using, including questions and option labels; keep command names, flags, file paths, skill names and other technical names unchanged.
| Mode | When | Read |
| Start | New to the plugin or unsure how to begin | references/start.md |
| Contents | What the plugin contains or what exists for a purpose | references/contents.md |
| Explain | How a named skill, agent or script works | references/explain.md |
| Route | Which skill fits a situation | references/map.md |
Read the target file before describing it so the answer is current. The map lists all 17 skills, including fnl-setup (with add <feature>, instructions, check, scan and mode subcommands) and the user-only fnl-restore-point save-and-restore command: fnl-advisor owns both one opinion and committees, fnl-delegate owns spec coordinator sessions, and fnl-session-hygiene owns knowledge and handovers. Read a procedure reference only when the question concerns that procedure. Answer and stop: invoke nothing; leave the how-to to the target skill when it runs. On Codex the user types $ instead of / for skill commands; Claude Code and Antigravity use /. Skills the user types, such as fnl-setup, may be missing from your own skill list; do not warn the user that they are missing.
The plugin also ships three agents instructed to leave project files unchanged: fnl-reviewer, fnl-security-reviewer and fnl-navigator; the map covers all 47 distinct script names, review routing, receipts, judge, run hygiene, work records, context snapshots, quota on demand and advisory parallel slots.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.