autoresearch-hooks

Run pre- and post-iteration hooks around an autoresearch loop.

6|1|Updated Nov 23, 2023
One-click install
npx skills add https://github.com/gmcabrita/dotfiles --skill autoresearch-hooks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoresearch-hooks
Source: https://github.com/gmcabrita/dotfiles/tree/main/.pi/agent/skills/autoresearch-hooks
Command: npx skills add https://github.com/gmcabrita/dotfiles --skill autoresearch-hooks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides optional pre- and post-iteration hooks that can run external scripts around an autoresearch loop, enabling side effects like notifications, logging, or data persistence without modifying the core loop.

Core Features & Use Cases

  • Hook contracts: define before.sh and after.sh hooks that run around each iteration without altering the loop.
  • Non-intrusive extension: hooks are optional and ignored if not present or not executable.
  • Examples and templates: shipped examples show how to trigger searches, logging, or alerts from the autocomplete loop.

Quick Start

Copy an example hook into autoresearch.hooks/before.sh and make it executable, then copy an after.sh if you want post-iteration actions.

Frequently Asked Questions about autoresearch-hooks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run custom bash scripts before or after an automated research loop iteration?

Pre- and post-iteration hooks allow you to trigger notifications, logging, or data persistence around an automated research loop. By placing executable bash scripts in the hooks directory, you inject side effects without modifying the main iteration logic.

What is the best way to add logging or notifications to an autoresearch session without modifying the core code?

The best way to add logging or notifications is using pre- and post-iteration hooks. You place executable bash scripts at autoresearch.hooks/before.sh or after.sh to trigger alerts and logs around the loop without touching core code.

How do I set up pre-iteration and post-iteration hooks for an autoresearch workflow?

To set up hooks, copy a template into autoresearch.hooks/before.sh or after.sh and make it executable. The hooks follow a strict JSON-driven contract for passing input and output data during the research iteration.

Do I need to write hook scripts in bash to use pre-iteration automation in autoresearch?

Hook scripts need to be executable bash files placed at autoresearch.hooks/before.sh and after.sh. If these hook files are not present or not executable, the automation loop safely ignores them and runs without the auxiliary scripts.

Can I trigger external searches or alerts from the autoresearch loop without altering the main process?

Yes, you can trigger external searches or alerts by defining before.sh and after.sh hook contracts. These optional non-intrusive scripts execute around each iteration, enabling side effects like alerts without altering the main process.

What happens if my pre-iteration or post-iteration hook scripts are missing during an autoresearch session?

If pre-iteration or post-iteration hook scripts are missing or not executable, the automation loop ignores them. The session continues running normally without triggering the auxiliary scripts, ensuring the main process never breaks.