Repository inventory

kevinxft/personal-growth-skill

Skills indexed from this repository, with install-style signals scoped to the repo.
1 skills0 GitHub stars0 weekly installsGitHubOwner profile

Overview

This skill manages a closed-loop daily and weekly planning system designed to work with Obsidian. It writes and updates notes under a Growth/ folder, keeps daily task lists, runs weekly reviews, and auto-generates higher-level month/quarter/year summaries when appropriate. The tone is minimal: record tasks as-is and only offer decomposition when explicitly requested.

How this skill works

The skill creates and updates Markdown notes in Growth/{year}/ using ISO week numbering and fixed section blocks (e.g., ## 🧭 今日规划, ## 📌 本周总结). For daily use it ensures today’s note exists, optionally collects unfinished tasks from recent notes, asks for today’s task list, and writes them verbatim as - [ ]. For weekly use it aggregates this week’s items, surfaces top unfinished tasks, writes a concise summary and populates the next week’s plan. When crossing boundaries (new week/month/quarter/year) it checks for missing higher-level summaries and auto-generates minimal YAML-frontmatter notes with 5–8 bullet summary points.

When to use it

  • Start the system: say “init” or initialization to create Growth/{current year}/
  • Morning or daily planning: trigger with “daily”, “plan”, “today”, or “morning”
  • Create a blank journal: say “create diary” or equivalent
  • Weekly review: say “weekly”, “this week”, or “weekly review” (or run on Sunday)
  • Let the skill auto-generate month/quarter/year summaries during normal daily/weekly use when period boundaries are crossed

Best practices

  • Give tasks as simple lines or bullet lists; the skill writes them verbatim as checklist items
  • Don’t expect automatic task decomposition—ask explicitly if you want suggestions or breakdowns
  • Keep Obsidian vault consistent: all notes under Growth/{year}/ to enable reliable aggregation
  • Use the weekly review to convert top unfinished items into clear next-week actions
  • Trust the auto-summary behavior: it only adds minimal blocks and YAML frontmatter to generated files

Example use cases

  • Morning planning: collect today’s meetings, focus items, and errands; written directly to today’s note
  • Recover unfinished work: list yesterday’s unresolved checkboxes and choose which to carry over
  • Sunday closeout: run weekly review to get two actionable takeaways, one bottleneck, and next week’s Top 3
  • On month/quarter/year boundary: let the skill auto-create a short generated summary note for higher-level reflection
  • Create a blank diary file quickly with the correct frontmatter and planning blocks

FAQ

No. It only updates the specified planning and summary blocks and will not alter other parts of your notes.

How many items will auto-generated summaries include?

Each generated month/quarter/year note keeps to 5–8 concise points to avoid long prose.

Can I ask it to break tasks into subtasks or give execution advice?

Yes, but only when you explicitly request task decomposition or suggestions; by default it records tasks without advising.

1 skills

More from this maintainer
Other repositories and skills published under the same GitHub owner.
Skills library
Jump back to the full directory or explore grouped topics.
Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational