Agent skill

Flashlight

by will-ness-ai in will-ness-ai/skills

Shine a light into a wayfinder map's fog — work one direction now, out of frontier order, or redraw the map itself.

MITAuto-check passed

Install Flashlight

skills CLI
$ npx skills add will-ness-ai/skills --skill flashlight -a claude-code

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

GitHub CLI
$ gh skill install will-ness-ai/skills flashlight --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/will-ness-ai/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/flashlight .claude/skills/flashlight && 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
flashlight
GitHub stars
168
Token cost
~1.4k tokens
SKILL.md length
854 words
Files
2
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Shine a light into a wayfinder map's fog — work one direction now, out of frontier order, or redraw the map itself.

  • Works in 8 steps: Aim the beam → Zoom out → Create and claim the ticket → …
  • SKILL.md covers Two beams, Shine into the territory and Redraw the map
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Flashlight is an agent skill from will-ness-ai/skills. Shine a light into a wayfinder map's fog — work one direction now, out of frontier order, or redraw the map itself.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

The repository describes itself as: Skills for building high quality software. The licence is MIT.

Example prompts

  • “/flashlight”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Aim the beam
  2. Zoom out
  3. Create and claim the ticket
  4. Work the ticket
  5. Record and adjust the map
  6. Read the whole chart
  7. Propose
  8. Apply

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    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

Flashlight loads about 1.4k tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 854 words of instructions outside code blocks.

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

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 will-ness-ai/skills at commit 71d8909, republished under its MIT licence (© will-ness-ai). 854 words, ~1,375 tokens.

Download SKILL.mdSave it as .claude/skills/flashlight/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
flashlight
description
Shine a light into a wayfinder map's fog — work one direction now, out of frontier order, or redraw the map itself.
disable-model-invocation
true

A wayfinder map charts a large effort as decision tickets on the issue tracker, wrapped in fog. Its frontier — the open, unblocked, unclaimed tickets — advances in its own order.

A flashlight is the human's beam. They point it at one direction, and this session walks in now, out of frontier order, to learn what lies that way.

/flashlight <map> <request>. Ask for the map when the invocation omits it. Shine one beam per session.

Where the map, its child tickets, blocking edges, claims and the frontier query physically live is tracker-specific. Consult the tracker doc's "Wayfinding operations" section for how this repo expresses each one. Default to the local-markdown tracker when no tracker doc is present.

Two beams

Read <request>, and ask one question: is the subject the map, or the territory?

  • Territory — the work itself. "Can we use SQLite for the queue?" → Shine into the territory.
  • Map — the chart you already drew: what to focus on, what to defer, what no longer belongs. "We have too many open tickets — what should we focus on?" → Redraw the map.

Ask the human to choose when the request reads both ways.

Shine into the territory

The beam becomes one ad-hoc ticket, and leaves the same trail as any ticket the map was charted with.

1. Aim the beam

Load the map — Destination, Notes, Decisions so far — and the open tickets bearing on the direction. Where an open ticket already asks this question, work that one instead: claim it, and continue from step 4.

Infer the type from the request:

TypeUse it forResolve with
Grilling (HITL)a decision to settle by conversation — the default/grilling and /domain-modeling
Research (AFK)a fact from outside this working directorya /research subagent
Prototype (HITL)"how should it look, how should it behave", answered by a cheap concrete artifact/prototype; /grill-design for an unsettled frontend look
Task (HITL or AFK)manual work that unblocks a decisionthe agent alone where it can; otherwise a precise checklist for the human

On a HITL type the human answers their own questions — this session asks and records. An AFK type runs alone.

Done when the type is chosen and the map's Destination is in hand.

2. Zoom out

Brief the human: the type in bold, what this session is about to do, and where the direction sits on the map.

Done when the human has seen the type before any ticket exists.

3. Create and claim the ticket

Create a child issue of the map titled Flashlight: <direction>, carrying the verbatim <request> as its question and the wayfinder:<type> label. It takes no blocking edges — it is born and closed inside this session.

Claim it — assign it to the dev driving the map — before the work starts.

Done when the ticket exists, carries its type, and shows an assignee.

4. Work the ticket

Resolve it as a ticket of its type. Invoke the skills the map's ## Notes names, plus the type's own. Zoom into any related or closed ticket on demand.

Done when the question has an answer its type can support.

Show full SKILL.md (341 more words)Show less
5. Record and adjust the map
  • Post the answer as a resolution comment, then close the ticket.
  • Append one line to Decisions so far: the ticket name, its link, and a one-line gist of the answer.
  • Create the tickets the answer made specifiable, and clear each graduated patch from Not yet specified.
  • Rule out of scope whatever the answer put past the destination: close it, and leave one line in Out of scope.

Done when the ticket is closed and every section the answer touched carries its line.

Redraw the map

The beam falls on the chart itself. This mode creates no ticket — the comments it leaves on the tickets it touches are the record.

1. Read the whole chart

Load the map and every open ticket: question, type, blockers, assignee.

Done when each open ticket is accounted for, the claimed ones included.

2. Propose

Show the human one change list, and wait for their approval. Name every edit, and why it earns its place.

Done when the human has approved the list.

3. Apply
VerbWhat it does
Createa new ticket — then wire its edges in a second pass, because issues need ids before they can reference each other
Updatea ticket's question
Re-ordermap order decides frontier order, so this is how you prioritise
Re-wirea ticket blocked by an open ticket leaves the frontier and returns when that blocker closes, so this is how you defer
Rule out of scopeclose it, and leave one line in Out of scope: the gist, and why it sits past the destination
Cancelfor a duplicate or a mistake. Close it, and leave one line in Decisions so far marked cancelled, carrying the reason

Comment on every ticket you touch, saying what happened and why.

A ticket with an assignee is claimed: a live session is working it right now. Leave its state as it is, and comment on it, so that session learns what changed.

Done when every approved edit is applied, and every touched ticket carries its comment.

© will-ness-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/flashlight of will-ness-ai/skills.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 71d8909

Compare with similar skills

Flashlight 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.

Flashlight compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Flashlight this skillwill-ness-ai/skills168—~1.4kAutomated safety check: PassMIT
Token Mapnexu-io/open-design100k—~1.4kAutomated safety check: PassApache-2.0
Maps Geographyasgeirtj/system_prompts_leaks69k—~717Automated safety check: PassCC0-1.0
Feature Maponyx-dot-app/onyx32k—~459Automated safety check: PassCustom licence
Source Mapsthedaviddias/Front-End-Checklist74k—~445Automated safety check: PassMIT
Customer Journey Mapphuryn/pm-skills27k—~816Automated safety check: PassMIT

Similar skills

  • Token Map

    nexu-io/open-design

    Map an extracted Figma / source-code token bag onto the active OD design system, producing a deterministic mapping the generate stage can consume.

    100k GitHub stars~1.4k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Maps Geography

    asgeirtj/system_prompts_leaks

    Accurate maps from real geo data — use for any map, or whenever geography would make a good graphic for a deliverable

    69k GitHub stars~717 tokensUpdated today
    Auto-check passed
  • Feature Map

    onyx-dot-app/onyx

    Use the Onyx feature map (.agents/feature-map/) to learn what a product surface does, the code behind it, and what a change can break.

    32k GitHub stars~459 tokensUpdated today
    Auto-check passed
  • Source Maps

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Provide source maps for production debugging.

    74k GitHub stars~445 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Customer Journey Map

    phuryn/pm-skills

    Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities.

    27k GitHub stars~816 tokensUpdated 23 days ago
    Product & Project ManagementAuto-check passed
  • Wayfinder

    vinvcn/mattpocock-skills-zh-CN

    把单个 agent session 装不下的一大块工作规划成 issue tracker 上的 decision tickets shared map,并逐一解决,直到通往 destination 的路清晰。

    4.7k GitHub stars~1.9k tokensUpdated 9 days ago
    DevelopmentAuto-check passed

More from will-ness-ai/skills

  • Cmux

    will-ness-ai/skills

    Drive the local cmux app — workspaces, panes, surfaces, terminal input, agent sessions, and browser surfaces.

    168 GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • Sandcastle

    will-ness-ai/skills

    Run a Sandcastle lane — a sandboxed implement→review loop over a fixed batch of work in its own worktree, ended by an agent-authored PR.

    168 GitHub stars~1.4k tokensUpdated today
    Auto-check: notes
  • Code Story

    will-ness-ai/skills

    Build a wizard-style HTML page that teaches how and why a change works.

    168 GitHub stars~828 tokensUpdated today
    Auto-check passed
  • Test A Skill

    will-ness-ai/skills

    Field-test a skill by running it cold in parallel agent sessions, then turn what they hit into edits.

    168 GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Grill Design

    will-ness-ai/skills

    Converge on a frontend look through rounds of prototypes and grilling verdicts.

    168 GitHub stars~254 tokensUpdated today
    Auto-check passed
  • Find Standards

    will-ness-ai/skills

    Find how this problem is already solved: standards we could adopt, and the industry's best practices.

    168 GitHub stars~585 tokensUpdated today
    Auto-check passed

Questions about Flashlight

What does Flashlight do?

Shine a light into a wayfinder map's fog — work one direction now, out of frontier order, or redraw the map itself. Flashlight is an agent skill from will-ness-ai/skills. Shine a light into a wayfinder map's fog — work one direction now, out of frontier order, or redraw the map itself.

How do I install Flashlight in Claude Code?

Run `npx skills add will-ness-ai/skills --skill flashlight -a claude-code`. Or copy the skill folder (skills/flashlight in will-ness-ai/skills) into .claude/skills/flashlight in your project. Claude Code loads it when a task matches its description.

How do I install Flashlight in Codex?

Run `npx skills add will-ness-ai/skills --skill flashlight -a codex`. Or copy the skill folder (skills/flashlight in will-ness-ai/skills) into .agents/skills/flashlight in your project. Codex loads it when a task matches its description.

Can I use Flashlight 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 will-ness-ai/skills --skill flashlight -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/flashlight, .gemini/skills/flashlight, .github/skills/flashlight and .opencode/skills/flashlight in your project.

What does Flashlight need to run?

SKILL.md names no scripts, command-line tools or credentials: Flashlight is instructions for the agent only.

Does Flashlight 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 Flashlight 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 Flashlight use?

Flashlight is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Flashlight use?

About 1.4k tokens (SKILL.md is roughly 5.5k 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 Flashlight?

Skills that share tags, products or a category with Flashlight: Token Map (nexu-io/open-design, 100k stars), Maps Geography (asgeirtj/system_prompts_leaks, 69k stars), Feature Map (onyx-dot-app/onyx, 32k stars) and Source Maps (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Flashlight?

will-ness-ai (a GitHub user) maintains it in will-ness-ai/skills, which has 168 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 8, 2026.

Source: will-ness-ai/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.