/seekter-report — how is the search going
SkillSearchSummarise the job search from the markdown tracker - funnel, response rate, what's working, where applications come from, what's pending on the user. Use when the user runs /seekter-report or asks how the search is going, for weekly numbers, or what to change.
Use /seekter-report — how is the search going in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add /seekter-report — how is the search going and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the /seekter-report skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Add Ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
What this skill tells your AI
The instructions your AI receives, as published by selfishprimate/seekter in .claude/skills/seekter-report/SKILL.md and read by Ahel’s review.
Read-only. Data comes from applications/ via scripts/seekter.py, plus runs/*.md for per-day source tables.
python3 scripts/seekter.py stats(all time) andpython3 scripts/seekter.py stats --since <7 days ago>.python3 scripts/seekter.py list --since <period start>, then read the front matter of the rows you need (source, ats, location_fit, fit).- Compute, for the period and all time:
- applications sent, skips, pending hand-offs;
- replies: interviewing + offer + rejected, as a share of sent; median days from
appliedto the first log line after it; - by
source(freehire, linkedin, board names, manual): sent and replies; - by
location_fit(A/B/C): sent and replies. A track with many sends and no replies is a targeting signal; - top skip reasons (group the Reason column of
applications/<YYYY-MM>/skipped.mdby its first clause).
- Every record with
status: pendingis a hand-off (python3 scripts/seekter.py list --status pending; also the "Needs you" table inapplications/README.md): list each with its link and the exact action. - Write 3–5 plain observations with the number behind each ("C-track: 14 sent, 0 replies in 3 weeks"). Suggest at most two changes, each tied to a file (
profile/search.jsonquery,profile/profile.mdrule). Don't change them without the user saying yes.
Save as runs/report-<YYYY-MM-DD>.md and show the user the short version.
Signals
- GitHub stars
- 56
- Forks
- 10
- Last commit
- Oct 2026
Advanced
- Item type
- skill
- Key
seekter-report- Source
- github.com/selfishprimate/seekter