Move bin/ scripts to scripts/ so the plugin installs on claude.ai

claude.ai-hosted plugins may not ship a top-level bin/ directory: its contents are added to PATH on the CLI but are not shown on the admin approval surface, so the platform rejects the plugin at install time (both repository-add and file upload). This blocked all claude.ai web and Cowork users from installing fusion-skills (issue #17); foundry-skills installs fine because it has no bin/.

These are not executable entry points. They are internal helpers (the Python venv-bootstrap chain: python.sh, python-detect.sh, setup-python-venv.sh) and repo dev tooling (cleanup_workflows.py, convert_catalog_to_yaml.py, export-trigger-yaml.sh), invoked by the skills and test harness rather than run as commands. bin/ is the only trigger, so the fix is relocation, not declaring them as commands or hooks. They move to a top-level scripts/ directory (shared across all four sub-skills, so not owned by any one skill's scripts/ dir), and every reference is updated: the four SKILL.md allowed-tools declarations and example commands, _bootstrap.py's wrapper path, hooks/bootstrap.sh, run-ab-test.sh, verify-workflows.sh, the test suite and conftest sys.path, and the CI shellcheck/pylint/pytest-cov globs.

Git detects all six as renames. Full local CI passes: 541 tests at 93.65% coverage, pylint 10.00/10, shellcheck clean, hook and scorecard suites green.

Author: mraible

.github/workflows/main.yml

@@ -18,7 +18,7 @@ jobs:
         run: command -v shellcheck || { sudo apt-get update -qq && sudo apt-get install -y -qq shellcheck; }
       - name: Run ShellCheck
         run: |
-          shellcheck hooks/*.sh bin/*.sh
+          shellcheck hooks/*.sh scripts/*.sh
           shellcheck --severity=error *.sh
 
   test-hooks:
@@ -69,7 +69,7 @@ jobs:
             --cov=skills/deployment/scripts \
             --cov=skills/execution/scripts \
             --cov=skills/lookup-files/scripts \
-            --cov=bin \
+            --cov=scripts \
             --cov-report=term-missing \
             --cov-fail-under=90
 
@@ -95,7 +95,7 @@ jobs:
             skills/deployment/scripts/*.py \
             skills/execution/scripts/*.py \
             skills/lookup-files/scripts/*.py \
-            bin/*.py
+            scripts/*.py
 
   validate:
     runs-on: ubuntu-latest

common/scripts/_bootstrap.py

@@ -2,14 +2,14 @@
 
 The skill's Python scripts depend on `crowdstrike-falconpy` (and `pyyaml`). Those
 live in a managed virtualenv at ``~/.cache/claude-code-fusion/venv``, created by
-the plugin's SessionStart hook and used by ``bin/python.sh``. But a script may be
+the plugin's SessionStart hook and used by ``scripts/python.sh``. But a script may be
 launched with a bare ``python script.py`` — for example from a cloned repo in dev
 mode, where the plugin hook never fired — using an interpreter that has no
 falconpy installed. That produces a ``ModuleNotFoundError`` at the first API call.
 
 ``ensure_deps()`` makes the scripts resilient to how they are launched: if the
 marker dependency (``falconpy``) is missing from the current interpreter, it
-re-executes the script through ``bin/python.sh``, which runs (and, on demand,
+re-executes the script through ``scripts/python.sh``, which runs (and, on demand,
 builds) the managed venv. If falconpy is already importable — the normal case,
 including when already running inside the venv — it does nothing.
 
@@ -33,13 +33,13 @@
 
 
 def _python_sh_path():
-    """Absolute path to bin/python.sh, resolved relative to this file.
+    """Absolute path to scripts/python.sh, resolved relative to this file.
 
     This module lives at ``<repo>/common/scripts/_bootstrap.py``; the wrapper is
-    at ``<repo>/bin/python.sh``.
+    at ``<repo>/scripts/python.sh``.
     """
     here = os.path.dirname(os.path.abspath(__file__))
-    return os.path.join(here, "..", "..", "bin", "python.sh")
+    return os.path.join(here, "..", "..", "scripts", "python.sh")
 
 
 def ensure_deps(script_path):

hooks/bootstrap.sh

@@ -5,8 +5,8 @@
 
 PLUGIN_ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
 
-"$PLUGIN_ROOT/bin/setup-python-venv.sh" >&2 || {
-    echo "fusion-skills: venv bootstrap did not complete; scripts may need a manual venv setup (bin/setup-python-venv.sh)." >&2
+"$PLUGIN_ROOT/scripts/setup-python-venv.sh" >&2 || {
+    echo "fusion-skills: venv bootstrap did not complete; scripts may need a manual venv setup (scripts/setup-python-venv.sh)." >&2
 }
 
 exit 0

run-ab-test.sh

@@ -93,7 +93,7 @@ find_workflow_file() {
 
 # Clean up deployed Fusion workflows from a phase directory.
 #
-# Deletes via the Workflows delete API (bin/cleanup_workflows.py, FalconPy
+# Deletes via the Workflows delete API (scripts/cleanup_workflows.py, FalconPy
 # delete_definitions) — no browser. Collects the workflow names deployed by each
 # run in the phase, then deletes them by name. Skipped entirely in --skip-deploy
 # mode, where nothing was imported.
@@ -117,9 +117,9 @@ cleanup_phase_workflows() {
     return 0
   fi
 
-  local cleanup_py="$REPO_ROOT/bin/cleanup_workflows.py"
+  local cleanup_py="$REPO_ROOT/scripts/cleanup_workflows.py"
   if [ ! -f "$cleanup_py" ]; then
-    echo "  NOTE: bin/cleanup_workflows.py not found — skipping cleanup."
+    echo "  NOTE: scripts/cleanup_workflows.py not found — skipping cleanup."
     echo "        Remove these manually in Falcon console → Fusion → Workflows:"
     printf '          - %s\n' "${names[@]}"
     return 0