Repository navigation
Add research-agent-skills - #12
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Hooray! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
There was a problem hiding this comment.
Thanks @jjans5 a welcome addition. The entry itself is right as it is: #11, merged just after you opened this, moved every entry to follow its plugin's main, so no ref is now the norm. Plugins in this marketplace should work alike, so three changes in research-agent-skills before I merge:
- Release by version bump. Add
"version": "0.1.0"to.claude-plugin/plugin.jsonand use the Release section the other plugins have: "Bumpversionin.claude-plugin/plugin.jsonand merge: the marketplace followsmain, and users update when the version changes." A merge tomainthen doesn't reach everyone at once; a release is a deliberate bump. Install can shrink to a pointer to this repo's README, as in euler-hpc. AGENTS.mdas the one instruction file. Claude Code now readsAGENTS.mditself when there is noCLAUDE.md(v2.1.277+, docs), and Codex reads it natively, so oneAGENTS.mdtracked in the repo serves both agents in every worktree, with no settings.analysis_templatealready does this. That makesproject-setup's rename toCLAUDE.md(§5) and the Codex config changes and marker files (§6) unnecessary: please switch the skill, its template andsetup_project.pytoAGENTS.mdand drop those two sections.- Worktrees under
.claude/worktrees/, whereclaude --worktree <name>creates them and analysis-workflow keeps them, instead of<project>/worktrees/<date>_<slug>.
Minor: research-workflow points to a token-lean skill "if it is installed"; no plugin here ships one, so drop the mention or add that skill to the marketplace.
|
Thanks @Marius1311, all three are done in quadbio/research-agent-skills#1, now merged (
Minor: the The entry in this PR is unchanged (no |
Adds research-agent-skills to the marketplace: three on-demand skills (no hooks) for research projects where agents write code, run compute and hand work over.
analysis-coderesearch-workflowPLAN.mdbefore compute,PROGRESS.md/HANDOVER.md, briefs for subagents and Codex,runlock.py(one writer per output folder).project-setupCLAUDE.mdread by both Claude Code and Codex,CODE_MAP.md/ENVIRONMENTS.mddrafted by survey scripts,handover/index.How it relates to the existing plugins: in repos that enable
analysis-workflow@quadbio, all three skills defer to its conventions (AGENTS.md, task directories, worktrees, working objects), andproject-setup's survey detects such repos and says so. Cluster specifics stay ineuler-hpc, figures insci-figures.Unpinned on purpose. The entry has no
ref, and the plugin'splugin.jsonhas noversion. Claude Code then versions it by commit SHA, so every merge to itsmainreaches users with auto-update on, with no marketplace bump needed. The plugin's README documents this. Happy to switch to tag pinning like the other plugins if you prefer that for the marketplace.🤖 Generated with Claude Code