Repository navigation
Conversation
Teach the managed installer the repository-local Grok skill path so install, status, update, and uninstall track .grok/skills the same way as Codex, Claude, and Cursor.
Extend installer tests and CI dogfood so managed .grok/skills installs are discovered by fledge let find skills for host grok, then disappear after uninstall.
End-to-end proof: Grok host + Let find skillsRevision: Commandsfledge lanes run verify # pass
fledge lanes run audit # pass (gitleaks: no leaks)Installer → filesystem → Letbin/corvid-skills install agent-coordination --repo <consumer> --host grok
bin/corvid-skills install fledge-workflows --repo <consumer> --host grok
fledge let find skills --scope project --host grok --repo <consumer> --cwd <consumer> --jsonProject-scope discoveries (asserted):
bin/corvid-skills uninstall agent-coordination --repo <consumer> --host grok
fledge let find skills --scope project --host grok --query agent-coordination --jsonAfter uninstall: zero project-scope Installer tests now exercise this path when |
The CorvidLabs/let plugin build hook requires Bun; install it so the Grok placement proof can run fledge let find skills on ubuntu-latest.
CI green + Let proofRun: https://github.com/CorvidLabs/skills/actions/runs/30715657560 What CI executed
Local verification (same assertions)Project-scope Let hits after install:
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 444a6c0395
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| export PATH="${BUN_INSTALL}/bin:${PATH}" | ||
| command -v bun | ||
| bun --version | ||
| fledge plugins install CorvidLabs/let --yes --non-interactive |
There was a problem hiding this comment.
When the default branch or tags in CorvidLabs/let change, this integration step starts building and testing that new code while Fledge remains pinned to v1.7.2, so an unchanged skills commit can begin failing because of an upstream output, CLI, or build change. The assertions also explicitly target the Let 0.2 payload shape; install a tested tag or revision using the owner/repo@tag source syntax documented in README.md:21-24.
Useful? React with 👍 / 👎.
- Recognize openai as a managed host with .openai/skills/<skill> destination - Update installer usage, status, and auto-resolution for openai - Document OpenAI host in README compatibility table - Add installer tests covering openai install, status, uninstall, auto host, and Let skill discovery - Include openai in CI dogfood host loop
|
Superseded by #11, which merged the reviewed Grok lifecycle integration and its CI fixes. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 093e169df2
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| find . -mindepth 1 -print0 | LC_ALL=C sort -z | while IFS= read -r -d '' entry; do | ||
| if [[ -d "$entry" ]]; then | ||
| printf 'directory\0%s\0' "$entry" | ||
| elif command -v shasum >/dev/null 2>&1; then | ||
| printf 'file\0%s\0%s\0' "$entry" "$(shasum -a 256 "$entry" | awk '{print $1}')" | ||
| else | ||
| sha256sum "$file" | ||
| printf 'file\0%s\0%s\0' "$entry" "$(sha256sum "$entry" | awk '{print $1}')" |
There was a problem hiding this comment.
When a repository contains an install created by the previous catalog version, its manifest stores the old file-only digest, but this new algorithm always produces a different path/type-aware digest for the unchanged directory. After upgrading the catalog, status therefore reports every existing install as modified, and the lifecycle guards refuse both update and uninstall; retain legacy-digest verification or version/migrate the digest format before switching algorithms.
Useful? React with 👍 / 👎.
| shell: bash | ||
| run: | | ||
| # Let’s fledge plugin build hook requires Bun. | ||
| curl -fsSL https://bun.sh/install | bash |
There was a problem hiding this comment.
When the Bun installer’s default release changes, this step begins building the pinned Let v0.2.0 plugin with a different runtime even though the skills commit is unchanged, so an upstream Bun regression or compatibility change can break this integration lane nondeterministically. Install an explicitly tested Bun version rather than executing the installer without a version selection.
Useful? React with 👍 / 👎.
1 participant
Summary
grok→ repository-local.grok/skills/<skill>--host autothe same as Codex, Claude, Cursorfledge let find skills --host grokDepends on #8 (managed skills lifecycle).
Exact Let evidence (local dogfood)
Result (project-scope rows only; Let 0.2 may also federate user-global Grok skills):
agent-coordinationgrokproject.grok/skills/agent-coordination/SKILL.mdfledge-workflowsgrokproject.grok/skills/fledge-workflows/SKILL.mdAfter uninstall:
→ no project-scope
agent-coordinationunder the consumer repo.Test Plan
fledge lanes validate . --strictfledge lanes run verify(installer tests include Let find skills whenfledge letis available)fledge lanes run audit(gitleaks clean)grok(table above)grok+ “Prove Grok placement with Let find skills”Usage
fledge plugins install CorvidLabs/skills fledge skills install agent-coordination --host grok fledge let find skills --scope project --host grok --json fledge skills uninstall agent-coordination --host grok