feyman-coach
ReviewAudited by ClawScan on May 10, 2026.
Overview
This appears to be a coherent learning-coach skill, but it can scan local Markdown notes and optionally run on a schedule or push generated review files to GitHub.
This skill is reasonable for a personal knowledge vault, but review the full helper script before scheduling it, run it from the correct notes directory, and be careful with the optional GitHub workflow if your notes or generated review files are private.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If run from a broad directory, the skill may inspect more personal Markdown notes than the user intended and store derived titles, paths, and review tasks.
The script defaults to the current directory and recursively reads Markdown file contents to select notes and generate review material.
"vault_path": "." ... for md_file in self.vault_path.rglob("*.md"): ... content = md_file.read_text(encoding="utf-8", errors="ignore")Run it from the intended notes vault only, use a narrow configuration, and try the list or dry-run mode before enabling automation.
Once enabled, the review generator can run every day without a per-run prompt.
The README explicitly instructs users how to create a daily scheduled task for the helper script.
$trigger = New-ScheduledTaskTrigger -Daily -At 9am Register-ScheduledTask -Action $action -Trigger $trigger -TaskName "FeynmanDailyReview"
Only create the scheduled task if you want daily automation, and know how to disable or delete the task if your needs change.
Generated review files containing note titles and paths could be committed to a shared or public repository if the user enables this workflow.
The optional GitHub Actions example runs on a schedule and pushes generated review files back to the repository.
on:
schedule:
- cron: '0 9 * * *'
...
git add Z_Utils/feynman-coach/daily-reviews/
...
git pushUse a private repository or review branch, confirm GitHub Actions write permissions, and avoid enabling this workflow for notes you do not want synced.
Installing optional packages from PyPI adds normal third-party dependency risk.
The README suggests optional PyPI dependencies without version pins; this is common for optional setup but still relies on external package provenance.
pip install tomli ... pip install win10toast
Install optional dependencies only if needed, preferably in a virtual environment, and pin or review package versions for long-term use.