golang learning

Engineering Community

Skill notes

Step 1 — Read History

Before generating any content: Read history.yaml from the skill directory (.agent/skills/golang-learning/history.yaml) Extract the list of all previously covered topics (the topic_key field of each entry) Also note the most recent entry's date so you can inform the user of their streak If history.yaml does not exist yet, treat the history as empty and create the file after the session.

Step 2 — Select Today's Topic

Pick one topic from the curriculum below that: Has NOT appeared in history.yaml Is appropriate as the next step given what topics have already been covered (prefer sequential/progressive ordering) If all topics in a category are covered, move to the next category Topic Curriculum (ordered by progression):

Step 3 — Generate the Daily Learning Session

Generate a full, structured learning session directly inside the pages/development/golang/ directory (the GitHub Pages site directory). Naming convention: Use YYYY-MM-DD_golang{NN}.md where NN is a 2-digit sequence (usually 01 for the first topic of the day). File path: pages/development/golang/YYYY-MM-DD_golang01.md (e.g., pages/development/golang/2026-03-08_golang01.md) Output Format

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1 — Read History

Before generating any content: Read `history.yaml` from the skill directory (`.agent/skills/golang-learning/history.yaml`) Extract the list of all previously covered topics (the `topic_key` field of each entry) Also note the most recent entry's date so you can inform the user of their streak If `history.yaml` does not exist yet, treat the history as empty and create the file after the session.

02
Step 2 — Select Today's Topic

Pick one topic from the curriculum below that: Has NOT appeared in `history.yaml` Is appropriate as the next step given what topics have already been covered (prefer sequential/progressive ordering) If all topics in a category are covered, move to the next category Topic Curriculum (ordered by progression):

03
Step 3 — Generate the Daily Learning Session

Generate a full, structured learning session directly inside the `pages/development/golang/` directory (the GitHub Pages site directory). Naming convention: Use `YYYY-MM-DD_golang{NN}.md` where NN is a 2-digit sequence (usually 01 for the first topic of the day). File path: `pages/development/golang/YYYY-MM-DD_golang01.md` (e.g., `pages/development/golang/2026-03-08_golang01.md`) Output Format

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.