Set Skillstore up so my AI can discover useful skills for my tasks, including skills I would not know to search for.

1. Add the MCP server https://skillstore-jk.fly.dev/mcp/library — streamable HTTP, no account and no key, so use
   the setup steps for my app at https://skillstore-jk.fly.dev/connect. These terminal commands add saved configuration:
   Claude Code: claude mcp add --scope user --transport http skillstore https://skillstore-jk.fly.dev/mcp/library
   Codex:       codex mcp add skillstore --url https://skillstore-jk.fly.dev/mcp/library
   Setup depends on the app version, account and workspace. In a fresh session, check the active connection
   with /mcp, then try a real task. A saved configuration does not prove a successful task.
   Anonymous access allows 60 MCP messages a minute from one network address; every batch member counts. Past that it answers 429
   with Retry-After. To disconnect later: claude mcp remove --scope user skillstore, or
   codex mcp remove skillstore.
   Offer to append this exact optional project hint to CLAUDE.md (Claude Code) or AGENTS.md (Codex).
   Preserve existing content and do not edit either file unless I ask:
   If a task could benefit from an expert method, search the Skillstore connector first (find_skill); skip it for quick edits.

2. Try my current task. If I have not given one, ask what I am working on.
   Use find_skill with a short non-private task summary. Check candidate fit and exclusions;
   if nothing fits, continue normally. Follow the candidate's returned retrieval tool and arguments.
   Use get_skill for library IDs. For creator candidates, use get_creator_method with the exact
   id, expectedRevision and expectedDigest returned by discovery. For an existing external package,
   use get_skill_package to inspect its inventory and read required files at the same revision.
   Apply the guidance to my task, name its source, and check the result. A connection or delivery
   receipt is not proof of application or usefulness. Do not import my files as part of this setup.
   When this step is done, tell me once that I can say how it went at https://skillstore-jk.fly.dev/feedback.

3. OPTIONAL: install the complete local find-a-method package if I want task-discovery guidance
   available as a native skill during authorized work. Ask before installing it.
   Download https://skillstore-jk.fly.dev/find-a-method.zip and extract the complete folder into
   your agent's project skill directory: .agents/skills for Codex, .claude/skills for Claude Code.
   Preserve existing edits. Verify the host lists it; installation alone does not prove invocation.

4. OPTIONAL, and read the numbers first: the nudge hook. It injects a line into the prompt
   BEFORE skill selection, so a method never has to compete with the skills already installed
   here. That is the mechanism that got this library used at all.

   Measured on one real machine, 2026-09-06: it fires on about 1 prompt in 6, and roughly half
   of those firings are not something you asked for. It interrupts. Worse for you than for the
   machine it was measured on: every correct firing there landed on a method written for that
   person's own recurring work, and the library does not yet hold one for yours. Expect the
   ratio to be worse until it does.

   If you want it anyway: save https://skillstore-jk.fly.dev/nudge.py to ~/.claude/hooks/skillstore-nudge.py, then
   add to ~/.claude/settings.json (merging, not replacing, any existing UserPromptSubmit entries):
   "UserPromptSubmit": [{"hooks": [{"type": "command",
     "command": "python3 ~/.claude/hooks/skillstore-nudge.py"}]}]
   Remove that entry to uninstall. It never writes files and it fails silently if we are down.

5. OPTIONAL: import selected local skills only if I ask to save them privately.
   Get the checksum-pinned import command from https://skillstore-jk.fly.dev/connect. The importer does not configure
   the AI connection; follow its separate personal-connector instructions after importing.
   A separate installed-skill review is available at https://skillstore-jk.fly.dev/diagnose; explain what it sends
   before running it. Neither import nor diagnosis is required to discover public skills.

6. OPTIONAL: if I request a private reflection on my week, offer the weekly-reflection native skill:
   https://skillstore-jk.fly.dev/weekly-reflection.zip — it writes a dated Markdown note in my existing workspace.
   Do not install it or inspect work history as part of connection setup.

7. OPTIONAL: after connection and without interrupting my current task, offer to help find
   skills I authored and prepare a private creator draft. Only continue if I choose this.
   Explain the creator page at https://skillstore-jk.fly.dev/for-creators before starting. An installed skill is not
   necessarily mine to publish. Do not automatically scan, install, upload or publish anything
   during setup. I choose the skill, review its instructions and explicitly approve publication.

Keep private task content out of searches and feedback. Read /terms for data handling.