@yy has a Claude Scholar project that tries to use #AI for benefits without the downsides:
"The key design principle is that these skills don’t try to do the thinking, researching, or writing for you [...] Instead, the plugin focuses on concrete, verifiable tasks that are tedious to do by hand but where correctness is easy to check."
@yy My impression of the accessible-pdf skill is using #AI once to create a script would lower the time and cost of future runs.
https://github.com/yy/claude-scholar/blob/main/skills/accessible-pdf/SKILL.md
If you have a collection of "skills" which are scriptable, I recommend a framework like `sub`. The idea is that you write scripts in any language dropped into a folder with a structured comment on the block, and you could end up with a personal CLI like:
yy help
yy accessible-pdf ./in.latex ./out.pdf
yy ...
@yy `sub` works fine-. It's simple shell scripting with no dependencies, but if you use it enough, it does have downsides. A more modern take is `tome`, written in Rust.
The differences and a link to Tome are here:
Mark Stosberg
YY Ahn