chore: untrack tracker CSV, scope scraper Bash permission, fix portal SKILL.md paths (#71)

- Untrack job_search_tracker.csv: it was both tracked and listed in
  .gitignore (same inconsistency class as the settings.local.json fix
  in #27). Users' personal rows risked merge conflicts on every pull;
  commands already create the file with the standard header when it
  is missing.
- Scope job-scraper's allowed-tools Bash entry (from #52) to
  'bun --version' and the portal-CLI invocation pattern, adopting the
  tighter form proposed in #65.
- Fix all five portal SKILL.mds documenting 'bun run skills/...'
  paths that do not resolve from the repo root ('.agents/skills/...'
  is correct) - now load-bearing since #52 wired /scrape to read
  these docs for CLI invocations. Surfaced in #66.
- Teach tools/lint_skills.py to glob-expand allowed-tools bun run
  targets so scoped wildcard permissions lint correctly.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Mads Lorentzen
2026-07-08 17:14:39 +02:00
committed by GitHub
co-authored by Claude Fable 5
parent 3c7a1cfdf5
commit a5ffcc39ff
8 changed files with 72 additions and 65 deletions
+7 -7
View File
@@ -11,7 +11,7 @@ description: >
positions open, remote jobs, "are there any X jobs in <place>", look up this
job posting.
context: fork
allowed-tools: Bash(bun run skills/linkedin-search/cli/src/cli.ts *)
allowed-tools: Bash(bun run .agents/skills/linkedin-search/cli/src/cli.ts *)
---
# LinkedIn Search Skill
@@ -42,7 +42,7 @@ Run it on your own responsibility.
### Search job listings
```bash
bun run skills/linkedin-search/cli/src/cli.ts search --location "<place>" [flags]
bun run .agents/skills/linkedin-search/cli/src/cli.ts search --location "<place>" [flags]
```
Key flags:
@@ -57,7 +57,7 @@ Key flags:
### Fetch full job detail
```bash
bun run skills/linkedin-search/cli/src/cli.ts detail <id|url> [--format json|plain]
bun run .agents/skills/linkedin-search/cli/src/cli.ts detail <id|url> [--format json|plain]
```
`id` is the job ID from `search` results (e.g. `4426311357`). You may also pass a full
@@ -68,16 +68,16 @@ seniority, employment type, job function, industries, and apply link.
```bash
# Data engineer roles in Bengaluru, last 30 days
bun run skills/linkedin-search/cli/src/cli.ts search -q "data engineer" -l "Bengaluru, Karnataka, India" --jobage 30 --format table
bun run .agents/skills/linkedin-search/cli/src/cli.ts search -q "data engineer" -l "Bengaluru, Karnataka, India" --jobage 30 --format table
# Product manager roles in Berlin, remote
bun run skills/linkedin-search/cli/src/cli.ts search -q "product manager" -l "Berlin, Germany" --remote remote --format table
bun run .agents/skills/linkedin-search/cli/src/cli.ts search -q "product manager" -l "Berlin, Germany" --remote remote --format table
# Any role, fully remote
bun run skills/linkedin-search/cli/src/cli.ts search -q "paralegal" -l "Remote" --format table
bun run .agents/skills/linkedin-search/cli/src/cli.ts search -q "paralegal" -l "Remote" --format table
# Full details for a specific job
bun run skills/linkedin-search/cli/src/cli.ts detail 4426311357 --format plain
bun run .agents/skills/linkedin-search/cli/src/cli.ts detail 4426311357 --format plain
```
## Output formats