board-recommend
Skill0 starsChanged 4 months agoMITView on GitHub
Recommend a suitable surfboard from rider ability, body parameters, board history, target waves, and available new, used, or rental options.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- log-sessionSkill
- scanSkill
- setup-surfSkill
- surfSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 10 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read data/profile.md first.
- Distinctive: line 23
If board fields are incomplete, ask one compact batch for:
- Distinctive: line 34
Do not require unrelated personal data.
- Distinctive: line 67
Never invent dimensions from a model name.
- Very specific: line 70
Write recommendations only to data/boards/recommendations.md.
- Distinctive: line 76
Verify manufacturer specifications, construction, included fins, warranty, lead time, and local availability.
- Distinctive: line 79
Do not recommend ordering custom dimensions without explaining the uncertainty.
- Distinctive: line 85
Ask for repair history, clear photos, dimensions, and volume.
- Distinctive: line 90
Verify the exact model or at least dimensions, volume, construction, and fin setup.
- Distinctive: line 92
Check rental duration, swap policy, damage terms, deposit, pickup hours, and whether the recommended size can be reserved.
- Distinctive: line 94
Prefer operators that allow board swaps when conditions change or the first choice proves unsuitable.
- Distinctive: line 109
Do not contact a shop, seller, owner, or rental operator.
≈ “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
Board recommendation
Recommend a board for the user's request using
method/board-recommendation.md.
Profile first
Read data/profile.md first. If it is missing, stop and offer /setup-surf;
do not infer body parameters or ability from repository examples.
Then read:
data/boards/history.mdif it existsdata/boards/fit-calibration.mdif it exists- the active location pack when destination waves matter
If board fields are incomplete, ask one compact batch for:
- weight and height;
- ability and surf frequency;
- current board dimensions, volume, construction, and verdict;
- two successful and unsuccessful past boards, if available;
- duck-dive, paddle, stability, durability, and turning priorities;
- target waves and progression goal;
- destination, trip/session duration, budget, and available acquisition modes: new, used, rental, or any.
Do not require unrelated personal data.
Recommend the board before the acquisition mode
Build a rider-and-wave brief:
- target shape family and why;
- a range, not a single magic volume;
- useful length/width/thickness/foil/rail/tail/fin characteristics;
- hard walk-aways and flexible trade-offs;
- target waves and conditions.
Base the range primarily on successful board history. Litres per kilogram is a comparison tool, not a universal ability formula.
The core recommendation must remain valid whether the board is new, used, or rented. Acquisition mode changes availability, price, condition, and commitment; it does not change the rider's fundamental fit.
Research available options
Because inventory and prices change, verify options live. For each candidate capture:
- URL and retrieval date;
- acquisition mode: new | used | rental;
- price and currency, including rental duration where relevant;
- stated dimensions, volume, construction, fins, condition, and repairs;
- fit against the brief;
- unknowns to ask the shop, owner, or rental operator;
- availability and size certainty;
- confidence and sources for model specifications.
Never invent dimensions from a model name. Use two independent sources for model specifications where possible; otherwise label them unverified.
Write recommendations only to data/boards/recommendations.md.
Acquisition-specific checks
New board
- Verify manufacturer specifications, construction, included fins, warranty, lead time, and local availability.
- Separate catalogue claims from independent information.
- Do not recommend ordering custom dimensions without explaining the uncertainty.
Used board
- Separate seller statements from verified model specifications.
- Apply the inspection checklist in
method/board-recommendation.md. - Ask for repair history, clear photos, dimensions, and volume.
- Compare price only when current local evidence exists.
Rental board
- Verify the exact model or at least dimensions, volume, construction, and fin setup; do not accept “mid-length” or “hybrid” as sufficient detail.
- Check rental duration, swap policy, damage terms, deposit, pickup hours, and whether the recommended size can be reserved.
- Prefer operators that allow board swaps when conditions change or the first choice proves unsuitable.
Rank and answer
Return:
- Recommended target specification.
- Ranked available options with fit verdict: strong | plausible | poor | insufficient information.
- Trade-offs caused by new, used, or rental availability.
- Missing information and the smallest next action.
Transaction boundary
Do not contact a shop, seller, owner, or rental operator; reveal private contact details; make an offer; reserve a board; buy; or rent anything without the user's explicit instruction.
Finish with the smallest next action: verify inventory, request specs/photos, inspect a used board, compare candidates, reserve a rental with approval, or walk away.
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.

