agentleFS
Sign inStart free
jmarek41jmarek41/surf-guide/.agents/skills/scan/SKILL.md

scan

Skill0 starsChanged 4 months agoMITView on GitHub

Scan configured short-trip destinations for exceptional reachable surf windows, then price flights only for confirmed candidates.

35 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use coverage, metrics and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • PydanticSkill

    coverage

    Fetch coverage diff from Codecov for the current branch or a specific PR. Shows uncovered lines, patch coverage, and overall coverage change.

    Also in 4 projects that use this

  • GoogleSkill

    metrics

    Expertise in analyzing time-series repository health metrics, investigating root causes, and proposing proactive workflow improvements.

    Also in 3 projects that use this

  • MicrosoftSkill

    report

    Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.

    Also in 5 projects that use this

  • anombyte93Skill

    discover

    Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.

    Also in 3 projects that use this

  • tuistSkill

    migrate

    Migrates existing Xcode projects to Tuist generated workspaces with build and run validation, external dependency mapping, and migration checklists. Use when adopting Tuist for an existing app or converting a hand-edited Xcode project to generated projects.

    Also in 3 projects that use this

  • Google CloudSkill

    fix

    Plan a remediation strategy after a test failure.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 32 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If data/profile.md is absent, stop the scan and offer /setup-surf.

    line 29
  2. Very specific:

    If data/scan/config.md is absent, create it from templates/scan-config.md after asking one compact batch for:

    line 32
  3. Distinctive:

    Never store an exact home address.

    line 43
  4. Very specific:

    Before the first run, create any missing log files from templates/scan-log.md and templates/flight-price-log.csv.

    line 46
  5. Distinctive:

    Run the cheap, batched swell triage for configured catalog cells.

    line 53
  6. Distinctive:

    If SerpAPI is not configured, continue the surf scan and provide pre-filled Google Flights links.

    line 61

“Common” is measured: kept by at least 6 in 10 of the 32 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Short-trip surf scan

Answer: “Is any configured destination about to be worth a short surf trip?”

Follow:

  • method/scan-workflow.md
  • method/flight-sources.md
  • scan/destinations.md
  • method/forecasting-principles.md
  • method/forecast-sources.md

Private configuration

Read:

  • data/profile.md
  • data/scan/config.md
  • data/scan/catalog-overlay.md if it exists
  • data/scan/scan-log.md if it exists
  • data/scan/flight-price-log.csv if it exists

If data/profile.md is absent, stop the scan and offer /setup-surf; do not invent rider ability, surf thresholds, or hard exclusions.

If data/scan/config.md is absent, create it from templates/scan-config.md after asking one compact batch for:

  • origin airports and acceptable ground-transfer time;
  • included destinations or all;
  • target face-height band and minimum period;
  • cleanliness and crowd requirements;
  • maximum nights and travel/surf ratio;
  • board-rental requirement;
  • currency and any price preference.

Never store an exact home address. Airport codes and an approximate home city are sufficient.

Before the first run, create any missing log files from templates/scan-log.md and templates/flight-price-log.csv. Preserve an existing log exactly; never replace it with the template.

Run

  1. Resolve and state the exact scan window. Default to the next 7–10 days.
  2. Run the cheap, batched swell triage for configured catalog cells.
  3. Deep-confirm only candidates, following the source and geometry gates.
  4. Classify each result as GO, near-GO, watch, or no-go.
  5. Price flights only for GO and near-GO candidates.
  6. Rank by surf opportunity first. Price, crowd, and travel are clearly shown, not hidden.
  7. Append the private scan and flight-price logs.

If SerpAPI is not configured, continue the surf scan and provide pre-filled Google Flights links. Never ask the user to paste a private key into chat.

Safety and authority

Forecasts and prices are volatile. State retrieval times and sources. Do not book travel, reserve equipment, contact an operator, or spend money without explicit user instruction.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free