New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Test Autocomplete

by walkthru-earth in walkthru-earth/geocoding-playground

Tests the smart autocomplete engine against known test scenarios from the study docs.

CC-BY-4.0Auto-check passed

Install Test Autocomplete

skills CLI
$ npx skills add walkthru-earth/geocoding-playground --skill test-autocomplete -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install walkthru-earth/geocoding-playground test-autocomplete --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/walkthru-earth/geocoding-playground.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/test-autocomplete .claude/skills/test-autocomplete && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
test-autocomplete
GitHub stars
153
Token cost
~587 tokens
SKILL.md length
202 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
CC-BY-4.0

At a glance

Tests the smart autocomplete engine against known test scenarios from the study docs.

  • Works in 5 steps: Read the test scenarios from… → Read the relevant source files → Trace the flow for the user's test case → …
  • The user asks to test autocomplete
  • SKILL.md covers Workflow and Key Constants to Check
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Test Autocomplete is an agent skill from walkthru-earth/geocoding-playground. Tests the smart autocomplete engine against known test scenarios from the study docs. Use this skill when the user asks to 'test autocomplete', 'verify search works', 'check the parser', 'test address parsing', 'run autocomplete tests', or wants to validate that a specific country's input classification and ranking works correctly. Also use after making changes to autocomplete.ts, address-parser.ts, or search.ts. Do NOT use for data investigation (use investigate-data instead) or UI testing.

Its SKILL.md is about 590 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with SQL. The repository describes itself as: Browser-based geocoder powered by DuckDB-WASM and Overture Maps, 469M+ addresses, zero backend. The licence is CC-BY-4.0.

When your agent uses it

  • The user asks to test autocomplete
  • Verify search works
  • Check the parser
  • Test address parsing

Example prompts

  • “test autocomplete”
  • “verify search works”
  • “check the parser”
  • “/test-autocomplete”

Requirements

  • Pre-approved tools (allowed-tools): Read, Grep, Glob

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Read the test scenarios from _study/AUTOCOMPLETE.md (Test Scenarios section).
  2. Read the relevant source files
  3. Trace the flow for the user's test case
  4. Check for regressions against the 3 known issues
  5. Report whether the code correctly handles the test case, with the exact

What it can do on your machine

Read from SKILL.md and the folder at commit d16cf53. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Test Autocomplete loads about 587 tokens when it runs. Until then it costs about 129 tokens; SKILL.md has 202 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~129
When it runs · the whole SKILL.md, loaded when a task matches
~587

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from walkthru-earth/geocoding-playground at commit d16cf53, republished under its CC-BY-4.0 licence (© walkthru-earth). 202 words, ~587 tokens.

Download SKILL.mdSave it as .claude/skills/test-autocomplete/SKILL.md (or your agent's skills folder).
name
test-autocomplete
description
Tests the smart autocomplete engine against known test scenarios from the study docs. Use this skill when the user asks to 'test autocomplete', 'verify search works', 'check the parser', 'test address parsing', 'run autocomplete tests', or wants to validate that a specific country's input classification and ranking works correctly. Also use after making changes to autocomplete.ts, address-parser.ts, or search.ts. Do NOT use for data investigation (use investigate-data instead) or UI testing.
allowed-tools
Read, Grep, Glob

Autocomplete Testing Skill

Validate the smart autocomplete engine against documented test scenarios.

Workflow

  1. Read the test scenarios from _study/AUTOCOMPLETE.md (Test Scenarios section).

  2. Read the relevant source files:

    • packages/core/src/autocomplete.ts - classifyInput(), suggest(), rankSuggestions()
    • packages/core/src/address-parser.ts - getParser(), POSTCODE_RE, NUMBER_FIRST
    • packages/core/src/search.ts - suggestionScore(), SearchCache

  3. Trace the flow for the user's test case:

    • What does classifyInput(input, cc) return? (street/postcode/mixed/ready)
    • What parser does getParser(cc) return?
    • What does parseAddress(input) extract? (street, number, postcode, unit)
    • What SQL would buildStreetSQL() or buildPostcodeSQL() generate?
    • How would rankSuggestions() order the results with the given city?
    • City search now uses searchCities() JS array search (not DuckDB SQL). It does prefix match with contains fallback + similarity ranking
    • preNormalize() can be used to pre-compute normalized names at prefetch time for faster search

  4. Check for regressions against the 3 known issues:

    • Issue 1: Duplicate cities (GROUP BY region, city dedup)
    • Issue 2: City boost in ORDER BY (list_has_any tile overlap)
    • Issue 3: Word match > prefix match (suggestionScore tiers)

  5. Report whether the code correctly handles the test case, with the exact classification, SQL, and ranking that would be produced.

Key Constants to Check

  • NUMBER_FIRST set in address-parser.ts must match pipeline SQL (addresses.sql line 143)
  • POSTCODE_RE patterns per country
  • suggestionScore tiers: 100=exact, 80=word, 60=prefix, 40=substring, 0-30=Jaccard

© walkthru-earth, CC-BY-4.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/test-autocomplete of walkthru-earth/geocoding-playground.

Open the folder on GitHubat commit d16cf53

Compare with similar skills

Test Autocomplete next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Test Autocomplete compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Test Autocomplete this skillwalkthru-earth/geocoding-playground153—~587Automated safety check: PassCC-BY-4.0
Excel and CSV Data Analysisbytedance/deer-flow84k4 repos~2.2kAutomated safety check: PassMIT
Clickhouse Logs Queriessupabase/supabase111k—~2.4kAutomated safety check: PassApache-2.0
Review PRapache/shardingsphere21k—~6.4kAutomated safety check: PassApache-2.0
Django Filter Benchmarksaleor/saleor23k—~2.3kAutomated safety check: PassBSD-3-Clause
Citus Check Style Reindentcitusdata/citus13k—~1.5kAutomated safety check: NotesAGPL-3.0

Similar skills

  • Excel and CSV Data Analysis

    bytedance/deer-flow

    Analyzes uploaded Excel and CSV files with SQL through DuckDB, producing schema inspections, statistical summaries and exports to CSV, JSON or Markdown.

    84k GitHub starsUsed in 4 repos~2.2k tokens
    Data & AnalyticsAuto-check passed

  • Clickhouse Logs Queries

    supabase/supabase

    Official

    Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint).

    111k GitHub stars~2.4k tokensUpdated today
    DatabasesAuto-check passed

  • Review PR

    apache/shardingsphere

    Review Apache ShardingSphere or user-authorized downstream pull requests and PR discussions from public or authorized repository evidence.

    21k GitHub stars~6.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Django Filter Benchmark

    saleor/saleor

    Benchmarks Django ORM filters in Saleor by generating bulk data, extracting the SQL and running EXPLAIN ANALYZE to check index usage.

    23k GitHub stars~2.3k tokensUpdated today
    DatabasesAuto-check passed

  • Citus Check Style Reindent

    citusdata/citus

    Fix a failing citusdata/citus check-style job by running make reindent with the exact uncrustify/citusindent versions the currently checked-out branch pins (read from its own STYLEGUIDE.md and its…

    13k GitHub stars~1.5k tokensUpdated yesterday
    DatabasesAuto-check: notes

  • Geoflow

    yaojingang/GEOFlow

    Operate/develop GEOFlow CLI/Laravel/admin/API, topics/专题 and topic tasks, theme libraries/replication, sites/leads/Agent, channel sync and legacy yao-geoflow-cli/design/template migration.

    3.8k GitHub stars~722 tokensUpdated yesterday
    Backend & APIsAuto-check passed

More from walkthru-earth/geocoding-playground

  • Investigate Data

    walkthru-earth/geocoding-playground

    Investigates geocoder data quality issues by querying live S3 parquet files via MotherDuck MCP.

    153 GitHub stars~935 tokensUpdated 3 mo ago
    Auto-check passed

Works with

Questions about Test Autocomplete

What does Test Autocomplete do?

Tests the smart autocomplete engine against known test scenarios from the study docs. Test Autocomplete is an agent skill from walkthru-earth/geocoding-playground. Tests the smart autocomplete engine against known test scenarios from the study docs.

When should I use Test Autocomplete?

Test Autocomplete fits situations like: the user asks to test autocomplete; verify search works; check the parser; test address parsing.

How do I install Test Autocomplete in Claude Code?

Run `npx skills add walkthru-earth/geocoding-playground --skill test-autocomplete -a claude-code`. Or copy the skill folder (.claude/skills/test-autocomplete in walkthru-earth/geocoding-playground) into .claude/skills/test-autocomplete in your project. Claude Code loads it when a task matches its description.

How do I install Test Autocomplete in Codex?

Run `npx skills add walkthru-earth/geocoding-playground --skill test-autocomplete -a codex`. Or copy the skill folder (.claude/skills/test-autocomplete in walkthru-earth/geocoding-playground) into .agents/skills/test-autocomplete in your project. Codex loads it when a task matches its description.

Can I use Test Autocomplete in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add walkthru-earth/geocoding-playground --skill test-autocomplete -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/test-autocomplete, .gemini/skills/test-autocomplete, .github/skills/test-autocomplete and .opencode/skills/test-autocomplete in your project.

What does Test Autocomplete need to run?

SKILL.md names no scripts, command-line tools or credentials: Test Autocomplete is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Glob.

Does Test Autocomplete access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Test Autocomplete safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Test Autocomplete use?

Test Autocomplete is published under the CC-BY-4.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Test Autocomplete use?

About 587 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Test Autocomplete?

Skills that share tags, products or a category with Test Autocomplete: Excel and CSV Data Analysis (bytedance/deer-flow, 84k stars), Clickhouse Logs Queries (supabase/supabase, 111k stars), Review PR (apache/shardingsphere, 21k stars) and Django Filter Benchmark (saleor/saleor, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Test Autocomplete?

walkthru-earth (a GitHub organization) maintains it in walkthru-earth/geocoding-playground, which has 153 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on June 24, 2026.

Source: walkthru-earth/geocoding-playground on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.