oss-bounty-finder
Find paid open-source work, OSS bounties, open source grants, or ways to get paid contributing to open source. Use when someone asks any of the following — "find me paid open source work", "show me OSS bounties for Rust", "how do I get paid for open source", "find GitHub bounties", "are there any open source grants I can apply to", "I want to earn money contributing to open source", "find bounties for Python developers", "show me open source funding opportunities", "what repos are paying for contributions", "find me issues with bounties", "show me open source stipends", "I want to contribute to open source and get paid", "find developer grants", "show me NLNet grants", "GSoC alternatives", "paid open source issues". Accepts a stack (Rust, Python, Go, TypeScript, etc.) and optional keywords. Runs a 3-tier parallel TinyFish agent system; Tier 1 scrapes Algora and IssueHunt, Tier 2 fans out across awesome-list repos checking for bounty-labelled issues, Tier 3 scrapes NLNet, Sovereign Tech Fund, Mozilla MOSS, LFX Mentorship, GSoC, and Outreachy. Synthesizes all findings into a structured paid opportunities report.
What this skill does
# OSS Bounty & Grant Finder — Find Paid Open Source Work
You have access to the TinyFish CLI (`tinyfish`), a tool that runs browser automations from the terminal using natural language goals. This skill uses it to search bounty platforms, GitHub repos, and grant foundation pages in parallel, then synthesizes results into a structured paid opportunities report.
## Pre-flight Check (REQUIRED)
Before making any TinyFish call, always run BOTH checks:
**1. CLI installed?**
PowerShell:
```powershell
Get-Command tinyfish; tinyfish --version
```
bash/zsh:
```bash
which tinyfish && tinyfish --version || echo "TINYFISH_CLI_NOT_INSTALLED"
```
If not installed, stop and tell the user:
> Install the TinyFish CLI: `npm install -g @tiny-fish/cli`
**2. Authenticated?**
```powershell
tinyfish auth status
```
If not authenticated, stop and tell the user:
> You need a TinyFish API key. Get one at: https://agent.tinyfish.ai/api-keys
>
> Then authenticate:
>
> **Option 1 — CLI login (interactive):**
> ```
> tinyfish auth login
> ```
>
> **Option 2 — PowerShell (current session only):**
> ```powershell
> $env:TINYFISH_API_KEY="your_api_key_here"
> ```
>
> **Option 3 — PowerShell (persist across sessions):**
> ```powershell
> [System.Environment]::SetEnvironmentVariable("TINYFISH_API_KEY", "your_api_key_here", "User")
> ```
> Then close and reopen PowerShell for it to take effect.
>
> **Option 4 — bash/zsh (Mac/Linux):**
> ```bash
> export TINYFISH_API_KEY="your_api_key_here"
> ```
>
> **Option 5 — Claude Code settings:** Add to `~/.claude/settings.local.json`:
> ```json
> {
> "env": {
> "TINYFISH_API_KEY": "your_api_key_here"
> }
> }
> ```
Do NOT proceed until both checks pass.
---
## What This Skill Does
Given a developer's stack and optional keywords (e.g. *"Rust, async"*), this skill:
1. **Tier 1** — Scrapes **Algora** and **IssueHunt**, bounty platforms that already curate paid OSS issues
2. **Tier 2** — Scrapes the **awesome-`<stack>`** GitHub list to discover top repos, then fans out to check each repo's bounty-labelled issues
3. **Tier 3** — Scrapes **NLNet, Sovereign Tech Fund, Mozilla MOSS, LFX Mentorship, GSoC, and Outreachy** for open grant calls
All three tiers run in parallel. Results are synthesized into a structured opportunities report.
---
## Core Command
```bash
tinyfish agent run --url <url> "<goal>"
```
### Flags
| Flag | Purpose |
|------|---------|
| `--url <url>` | Target website URL |
| `--sync` | Wait for full result (no streaming) |
| `--async` | Submit and return immediately |
| `--pretty` | Human-readable formatted output |
---
## Inputs
Ask the user for:
| Input | Required | Example |
|-------|----------|---------|
| `stack` | ✅ Yes | `Rust`, `Python`, `Go`, `TypeScript` |
| `keywords` | Optional | `async`, `cli`, `web3` |
| `min_amount` | Optional | `100` (minimum bounty $ to include) |
---
## Step-by-Step Workflow
### Tier 1 — Bounty Aggregator Platforms
Scrape Algora and IssueHunt in parallel. These platforms already curate and index bounties — one agent per platform.
**Algora:**
```bash
tinyfish agent run --sync \
--url "https://algora.io/bounties?lang=<stack>" \
"This is Algora.io, a paid OSS bounty platform filtered for <stack>. Extract all visible open bounty listings. Only include bounties relevant to <stack> — skip any for unrelated languages. Return as JSON array: [{\"title\": str, \"repo\": str, \"url\": str, \"bountyAmount\": number, \"currency\": str, \"skills\": [str]}]"
```
**IssueHunt:**
```bash
tinyfish agent run --sync \
--url "https://issuehunt.io/repos?language=<stack>" \
"This is IssueHunt, a paid OSS bounty platform filtered for <stack>. Extract all open bounty listings. Only include bounties relevant to <stack>. Return as JSON array: [{\"title\": str, \"repo\": str, \"url\": str, \"bountyAmount\": number, \"currency\": str, \"skills\": [str]}]"
```
**Example for Rust:**
```bash
tinyfish agent run --sync \
--url "https://algora.io/bounties?lang=rust" \
"This is Algora.io filtered for Rust. Extract all open Rust bounties. Skip any for Scala, Java, Python or other non-Rust stacks. Return as JSON array: [{\"title\": str, \"repo\": str, \"url\": str, \"bountyAmount\": number, \"currency\": \"USD\", \"skills\": [str]}]"
```
---
### Tier 2 — Awesome List → Repo Fan-Out
This is a two-stage process. Run Stage 2 agents in parallel once Stage 1 completes.
**Awesome list URLs by stack:**
| Stack | Awesome List URL |
|-------|-----------------|
| Rust | `https://github.com/rust-unofficial/awesome-rust` |
| Go | `https://github.com/avelino/awesome-go` |
| Python | `https://github.com/vinta/awesome-python` |
| TypeScript | `https://github.com/dzharii/awesome-typescript` |
| JavaScript | `https://github.com/sorrycc/awesome-javascript` |
| C++ | `https://github.com/fffaraz/awesome-cpp` |
| Java | `https://github.com/akullpp/awesome-java` |
| Swift | `https://github.com/matteocrippa/awesome-swift` |
| Elixir | `https://github.com/h4cc/awesome-elixir` |
| Zig | `https://github.com/catdevnull/awesome-zig` |
**Stage 2a — Discover repos from awesome list:**
```bash
tinyfish agent run --sync \
--url "https://github.com/<awesome-list-url>" \
"This is a GitHub awesome list. Extract GitHub repo URLs from the README. Return JSON: {\"repos\": [\"https://github.com/owner/repo\"]}. Rules: only owner/repo paths, skip wikis/gists/topics, skip the list repo itself, first 25 unique repos only."
```
**Stage 2b — Check each repo for bounty issues (run all in parallel):**
```bash
tinyfish agent run --sync \
--url "https://github.com/<owner>/<repo>/issues?q=is%3Aopen+label%3Abounty+OR+bounty+in%3Atitle+OR+reward+in%3Atitle" \
"This is a GitHub issues page. Extract all visible issues mentioning bounty, reward, or paid work. Return as JSON array: [{\"title\": str, \"repo\": str, \"url\": str, \"bountyAmount\": number or null, \"currency\": str or null, \"labels\": [str], \"skills\": [str], \"difficulty\": str}]. Return [] if no issues visible."
```
---
### Tier 3 — Grant Programs
Scrape all six grant foundations in parallel. These are language-agnostic — always run regardless of stack.
```bash
# NLNet / NGI Zero
tinyfish agent run --sync \
--url "https://nlnet.nl/thema/" \
"This is the NLNet grants page. Extract all currently open grant programs. Return as JSON array: [{\"title\": str, \"url\": str, \"bountyAmount\": number, \"currency\": \"EUR\", \"deadline\": str, \"description\": str, \"labels\": [\"grant\", \"nlnet\"]}]"
# Sovereign Tech Fund
tinyfish agent run --sync \
--url "https://www.sovereigntechfund.de/programs" \
"This is the Sovereign Tech Fund grants page. Extract all open programs. Return as JSON array: [{\"title\": str, \"url\": str, \"bountyAmount\": number, \"currency\": \"EUR\", \"deadline\": str, \"description\": str, \"labels\": [\"grant\", \"stf\"]}]"
# Mozilla MOSS
tinyfish agent run --sync \
--url "https://www.mozilla.org/en-US/moss/" \
"This is Mozilla MOSS grants page. Extract all open grant tracks. Return as JSON array: [{\"title\": str, \"url\": str, \"bountyAmount\": number, \"currency\": \"USD\", \"deadline\": str, \"description\": str, \"labels\": [\"grant\", \"mozilla\"]}]"
# LFX Mentorship
tinyfish agent run --sync \
--url "https://lfx.linuxfoundation.org/tools/mentorship/" \
"This is the LFX Mentorship page. Extract all open mentorship programs. Return as JSON array: [{\"title\": str, \"url\": str, \"bountyAmount\": number, \"currency\": \"USD\", \"deadline\": str, \"description\": str, \"labels\": [\"grant\", \"lfx\"]}]"
# Google Summer of Code
tinyfish agent run --sync \
--url "https://summerofcode.withgoogle.com/" \
"This is Google Summer of Code. Extract program details and open application info. Return as JSON array: [{\"title\": str, \"url\": str, \"bountyAmount\": number, \"currency\": \"USD\", \"deadline\": str, \"description\": str, \"labels\": [\"grant\", \"gsoc\"]}]"
# Outreachy
tinyfish agent run --sync \
--url "httRelated in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".