Scan GitHub activity and buildlogs to generate Obsidian-compatible content plans.
npx skills add https://github.com/Peleke/hunter --skill content-planner
Please help me install this Agent Skill. Skill: content-planner Source: https://github.com/Peleke/hunter/tree/main/skills/content-planner Command: npx skills add https://github.com/Peleke/hunter --skill content-planner
This Skill automates the process of identifying and planning publishable content directly from recent engineering work, bridging the gap between development activity and content creation.
Use the content-planner skill to scan the last 14 days of GitHub activity and buildlog entries to generate a content plan.
High-intent search queries and answers about installing and using this skill.
To generate content ideas from GitHub activity, this Skill scans merged PRs and buildlog entries to synthesize engineering work into publishable narratives. It bridges development and content creation by finding potential articles within recent codebase updates.
The best way to plan LinkedIn posts from engineering work is using fan-out analysis, which derives multiple content types from a single PR. It generates structured content briefs and outlines complete with source material links for easy execution.
Yes, you need Python 3 and specific GitHub CLI tools installed to automate content planning from repositories. These dependencies allow the Skill to scan GitHub activity and synthesize engineering work into publishable content opportunities.
Yes, you can manage content in Obsidian because the planner generates an Obsidian-compatible content plan. This includes a Kanban board and instrumented briefs to help you track writing ideas generated from recent engineering work.
Create an Obsidian Kanban board for engineering content briefs by scanning 14 days of GitHub activity and buildlog entries. The process outputs a structured markdown content plan designed for Obsidian management.
Content planning from GitHub activity requires buildlog entries to provide deeper context beyond code changes. Combining PRs with buildlogs allows the fan-out analysis to accurately synthesize engineering work into detailed content briefs.
PelekeTransform raw engineering logs into structured Obsidian notes for LinWheel.
cajiasUnescape HTML entities and publish markdown to Notion pages.
danburonlineFormat and edit Obsidian Markdown notes with wikilinks, embeds, callouts, and frontmatter.
paultyngAutomate Git pre-commit checks, changelog generation, and GitHub pull request updates.
