Skip to content

Add ax workflow recall skill - #10

Open
Necmttn wants to merge 1 commit into
yeaight7:mainfrom
Necmttn:add-ax-workflow-recall
Open

Necmttn wants to merge 1 commit into
yeaight7:mainfrom
Necmttn:add-ax-workflow-recall

Conversation

@Necmttn

@Necmttn Necmttn commented Jun 21, 2026

Copy link
Copy Markdown

Summary

  • Add ax-workflow-recall as a tool-dependent Agent Powerups skill
  • Document the ax CLI checks, approval-gated install path, and fallback behavior
  • Register the skill in catalog.json and the README tool requirements table

Checks

  • git diff --check
  • python3 scripts/validate-skills.py
  • python3 scripts/validate-catalog.py
  • python3 scripts/check-requirements.py ax-workflow-recall
  • banned copy-word scan

Generated with ax.

@yeaight7

Copy link
Copy Markdown
Owner

Hello @Necmttn!
Thanks for the submission!!!
Haven't had the time to take a look at it yet, but i will do soon!
The PR description looks OK and the validation seems fair.
Happy to merge this as soon as i take a look at it.

Great stuff 🚀

@yeaight7
yeaight7 self-requested a review June 25, 2026 08:29
@Necmttn

Necmttn commented Jun 25, 2026

Copy link
Copy Markdown
Author

Sounds good thank you 🙌

@yeaight7 yeaight7 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Necmttn Thanks again for the contribution. The asset shape itself looks aligned with this repo, and the repo-side plumbing is already covered by the existing skill/catalog/requirements validation, so I don't think this needs a CLI/source addition on my side.

One concern should block this PR for now: the documented install command is presented as installing the ax CLI, but the current installer does more than place a CLI binary by default. In particular, curl -fsSL ax.necmttn.com/install | sh defaults to running the follow-up axctl install flow where supported, which can set up local services/watcher/setup behavior. That is more side effect than the skill and README disclose, and this repo's policy for tool-dependent skills needs install steps to be explicit, approval-gated, and reviewable.

Could you update the skill and README row to either use a safer CLI-only install command, for example with --no-run-install, or clearly split the binary install from any later setup/ingest/service steps with separate explicit approval? Once that is made clear, I don't see a need for additional repo CLI changes for this contribution.

Apart from this concern, I don't see any other blocking issue. Just raising this concern to see what's your take on it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants