founder-coach

This skill is generally coherent for a coach that keeps a local profile and reads your journal files, but there are a few things to check before installing: 1) File writes: It will create ~/.founder-coach/config.yaml and files under ~/PhoenixClaw/Startup (founder-profile.md and weekly reports). If you use PhoenixClaw, confirm you want this skill to write into that vault rather than keeping coach data in a separate folder. 2) Automatic scheduling: The docs mention an automatic weekly report via cron, but there is no install step showing how a cron job would be added. Ask the author how automatic scheduling is implemented and whether it requires explicit user approval to create cron entries or background tasks. 3) Read access: The skill reads ~/.phoenixclaw/config.yaml and daily journal files to provide context. If you keep sensitive information in those journals, be aware the coach will read them when integration is enabled. 4) Guardrails clarity: The skill repeatedly states it 'must not' modify PhoenixClaw core data but also suggests optionally injecting coaching insights into journals—get clarification on exact write behavior and seek an explicit opt-in toggle for any writes to PhoenixClaw files. If you are comfortable with local file persistence and explicitly grant access to your PhoenixClaw vault (or keep the coach in standalone mode), the design is reasonable. If you prefer stricter separation, ask the maintainer to confine all coach files to ~/.founder-coach or another user-approved directory and to require an explicit opt-in before creating cron jobs or modifying any PhoenixClaw files.