The automation trap: I kept spending 2 hours to build 5-minute tasks. So I fixed it.

You know exactly what you want the workflow to do. Five steps. Twenty minutes of actual logic.

But you spend two hours on:

• Setting up API auth
• Wiring error handling
• Figuring out cron syntax
• Writing the boilerplate to read env vars
• Making the scheduler actually reliable

The workflow logic takes 20 minutes. The surrounding scaffolding takes 2 hours.

I had 10 of these workflows sitting on my "automate eventually" list for months. So I built skillforge — tell it what you want in plain English, get production-ready Python + a deployment config back.

How a session looks

$ skillforge new "every morning at 9am, summarize my open GitHub PRs and post to Slack"

Compiling skill...

Trigger: cron (0 9 * * 1-5)
Steps:
  1. fetch_prs — GitHub API, list open PRs
  2. summarize — Claude, generate standup summary
  3. post — Slack, post to #standup

Generated: ~/.skillforge/skills/morning-standup/
  skill.yaml
  skill.py

Run it now? [y/N]:

What you get

Two files, both human-readable:

skill.yaml — the manifest:

name: morning-standup
trigger:
  type: cron
  schedule: "0 9 * * 1-5"
steps:
  - name: fetch_prs
    tool: github
    action: list_open_prs
    output: prs
  - name: summarize
    tool: claude
    prompt: "Summarize for standup: {prs}"
    output: summary
  - name: post
    tool: slack
    action: post_message
    channel: "#standup"
    message: "{summary}"

skill.py — actual Python you can read, edit, and run directly. No framework lock-in.

Running and deploying

skillforge run morning-standup          # Run locally right now
skillforge deploy morning-standup       # Deploy as GitHub Action

skillforge deploy generates a .github/workflows/morning-standup.yml file. Push it, add your secrets, done. The cron runs forever with zero infrastructure.

What this is not

Not a no-code platform. Not a SaaS. Not a subscription.

skillforge generates code you own. Edit the Python. Modify the YAML. Delete skillforge and the skills keep running.

The community library

skillforge ships with 10 starter skills:

• morning-standup — PR summary → Slack
• github-digest — daily notification digest
• hn-monitor — Hacker News keyword alerts
• pr-review-reminder — ping stale PRs
• repo-health — weekly metrics report

skillforge install hn-monitor
skillforge run hn-monitor

The 10 workflows I automated

All 10 are now running. Total setup time per workflow: under 5 minutes. Total time I was spending manually: ~1 hour/day.

The one that surprised me most: hn-monitor. Set it up in 3 minutes. Been running for 2 weeks. Caught 4 mentions I would have missed.

The boilerplate trap is real. The fix is to stop writing the boilerplate.

GitHub: https://github.com/LakshmiSravyaVedantham/skillforge