- Python 98%
- Shell 2%
Kjell Tore Guttormsen
96af9526c1
Addendum to plan Step 1, which stays open: the four bullets are still `ubesvart` and the step's Verify still exits 1. Nothing measured changed. The previous instruction was one sentence -- "upload via Customize -> Plugins, run probe-versjon, check whether probe-tools appears" -- which assumed the reader already knew where each of those lives and what counts as an answer. The walkthrough now lives in the file the answers get written into, rather than in a chat message that scrolls away. Every UI path and caveat is sourced from research/03, not invented: the install-from-file and drag-into-chat routes, connectors appearing under the plugin's connectors page rather than as skills, the stale-cache issue (#69020) that makes the 0.0.1 version check load-bearing, and the upload-does-not- survive-relaunch report (#65426). Two distinctions are called out because getting them wrong would produce a confident wrong answer: - `- python3:` measures the SANDBOX interpreter, not the host's. Cowork runs shell commands in the VM or in the cloud. It is still the right thing to measure, but it says nothing about the virtualenv Step 2 built. - `- Host-MCP:` does run on the host, since local MCP servers were moved out of the sandbox in May 2026. A `ja` there is what decision 7 rests on, so it requires both that the connector is listed and that probe_ping answers -- "present but mute" is recorded as nei with a note, because absent and mute point at different causes. Section A is ordered first on purpose: cloud sessions are documented not to run local MCP servers, so `sky` plus a `ja` on Host-MCP would contradict the documentation and is a more interesting result than either answer alone. The verify command in section F was executed as written from the rendered document, not just pasted in: exit 1, as it must be while the probe is open. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .claude-plugin | ||
| docs | ||
| scripts | ||
| tests | ||
| .gitignore | ||
| CHANGELOG.md | ||
| CLAUDE.md | ||
| LICENSE | ||
| pyproject.toml | ||
| README.md | ||
jobbsok
Local-first job search workspace: sourcing, scoring, case tracking, applications and interview prep.
A read-only job search operating system for one person searching for their own job. It reads listings the operator is already looking at, scores them against a maintained candidate profile, records every accept/reject decision with a reason, keeps each case's full correspondence in one folder, drafts applications as files, and flags threads that have gone silent. It never submits, never sends, never stores a credential.
Solo-maintained, fork-and-own. This plugin is a starting point, not a vendor product. Issues are welcome as signals; pull requests are not accepted.
AI-generated: all code produced by Claude Code through dialog-driven development.
Status: pre-release. Nothing is built yet beyond the manifest; the build
brief in docs/build-brief.md is the contract, and milestones ship in order
(M1–M6).
Install
Not installable yet. When released, the plugin is pinned by tag in the
ktg-plugin-marketplace catalog:
claude plugin marketplace add https://git.fromaitochitta.com/open/ktg-plugin-marketplace.git
claude plugin install jobbsok@ktg-plugin-marketplace
Non-goals
Submitting applications. Sending email. Any write to Finn.no or LinkedIn. Credential storage. Background jobs. Multi-user support. Recruiter-side features. Bulk listing harvest.
Changelog
See CHANGELOG.md.
License
MIT — see LICENSE.