Nm Egregore Summon

This orchestrator appears to do what it says, but several mismatches and powerful side-effects mean you should not install it blindly. Before using it: - Verify prerequisites are present and explicit: ensure git, gh (GitHub CLI) and python3 are on PATH and authenticated as you intend. The skill expects these but doesn't declare them. - Review repository-local scripts referenced (scripts/deferred_capture.py, scripts/parallel.py, notify.py, manifest.py, prepare-pr logic). These run at runtime and may send network requests or push commits/PRs. - Check auto_merge and merge policy in the egregore config. If auto_merge:true is enabled, the skill may merge PRs without human review—disable or require manual steps if you want control. - Confirm notification behavior: inspect notify.py and any configured channels to understand what external systems are informed when rate limits or failures occur. Provide minimal-scope credentials and tokens only. - Run in a controlled environment first: try on a sandbox repo or with pipeline/auto-merge disabled and manual invocation to observe behavior. Back up important branches before allowing autonomous runs. - Limit agent autonomy if possible: run manually (not scheduled/autonomous) until you’ve validated its behavior, and monitor logs (.egregore/manifest.json, budget.json, continuation.json). If you can inspect the referenced scripts and provide explicit, least-privilege credentials for any external service the skill must use (and disable auto-merge), the remaining concerns become manageable. If you cannot inspect those files or do not want automated repo writes/notifications, treat this skill as unsuitable.