agentleFS
Sign inStart free
IgorGanapolskyIgorGanapolsky/ThumbGate/.agents/skills/thumbgate-daily-discoveries/SKILL.md

thumbgate-daily-discoveries

Skill29 starsChanged 7 months agoMITView on GitHub

Autonomous daily publishing engine and monitoring skill for ThumbGate news and technical discoveries. Generates high-density engineering posts with full UTM attribution, synchronizes to Obsidian, schedules dual cron/launchd runs at 9:00 AM EST, and tracks publication ledgers.

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All outbound links to thumbgate.ai must use buildUTMLink from scripts/social-analytics/utm.js.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

📰 ThumbGate Daily Technical Discoveries & News Engine

This skill automates the daily harvesting, synthesis, UTM attribution, and multi-channel publication of ThumbGate engineering discoveries and release news.

🎯 Architecture & Operating Principles

  1. Daily Cadence (9:00 AM EST): Runs once per calendar day. Avoids spam while establishing consistent technical authority.
  2. Dual Scheduling Redundancy:
    • Primary: macOS crontab (0 9 * * * /bin/bash scripts/thumbgate-daily-discoveries-publish.sh ...)
    • Fallback: macOS LaunchAgent (~/Library/LaunchAgents/com.thumbgate.daily-publish.plist)
    • Note: GitHub Actions schedule: is strictly limited to codeql.yml per repo hygiene tests.
  3. Full UTM Attribution & Tracked Redirects:
    • All outbound links to thumbgate.ai must use buildUTMLink from scripts/social-analytics/utm.js.
    • Outbound pro/checkout links must route through /go/pro (serveTrackedLinkRedirect in src/api/server.js) to capture first-party funnel telemetry.
  4. Multi-Surface Staging & Sync:
    • Staged locally at docs/marketing/daily-discoveries/YYYY-MM-DD-<slug>.md.
    • Synchronized to the CEO's Obsidian Vault at ~/Documents/Igor/Research/Daily-Discoveries/.
    • Logged idempotently to .thumbgate/daily-discoveries-ledger.jsonl.
    • Dispatches to Dev.to / Zernio if API keys are configured.

🛠️ CLI Commands & Usage

# Preview today's technical discovery without making mutations or network calls
node scripts/thumbgate-daily-discoveries-publish.js --dry-run

# Output structured JSON report
node scripts/thumbgate-daily-discoveries-publish.js --json

# Force publish/restage today's discovery even if already logged in ledger
node scripts/thumbgate-daily-discoveries-publish.js --force

# Shell wrapper (used by crontab / launchd)
./scripts/thumbgate-daily-discoveries-publish.sh

# Run test suite
node --test tests/thumbgate-daily-discoveries-publish.test.js

📋 Pre-Flight Verification Checklist

  • Verify node --test tests/thumbgate-daily-discoveries-publish.test.js passes.
  • Verify outbound links contain valid UTM parameters (utm_source=daily_discoveries, utm_campaign=daily_technical_discoveries).
  • Verify launchctl list | grep thumbgate reports exit code 0.
  • Verify crontab -l | grep thumbgate contains the 9:00 AM daily trigger.
  • Check .thumbgate/daily-discoveries-ledger.jsonl for recent execution receipts.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free