agentleFS
Sign inStart free
SaintChrisSaintChris/hermes-skills/skills/devops/open-source-contribution/SKILL.md

open-source-contribution

Skill0 starsChanged 5 months agoMITView on GitHub

Contribute to external open-source repos and publish across platforms. Covers discovery, scoping, writing, PR process, and multi-platform publishing (Dev.to, GitHub, LinkedIn). Use when the user wants to contribute to a repo, submit a PR, publish an article, share content, or distribute a skill to HermesHub.

  • Reads credentials
  • Commits and pushes

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. LinuxSuRen/my-dsh-skills★ 2same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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. Distinctive:

    Check repo activity: git log --oneline -20 or check GitHub Insights

    line 43
  2. Distinctive:

    Read CONTRIBUTING.md and templates

    line 45
  3. Distinctive:

    Use the repo's template exactly

    line 61
  4. Distinctive:

    Write factual, sourced content — no guessing

    line 62
  5. Distinctive:

    Document pitfalls and verification steps

    line 64
  6. Very specific:

    Run grep -n '^||' file.md to catch double-pipe markdown issues

    line 65
  7. Distinctive:

    Commit with descriptive messages

    line 70
  8. Distinctive:

    After merging, share your work:

    line 76

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Open Source Contribution + Publishing

Contribute to external open-source repos and publish your work across platforms. One workflow from discovery to published article.

When to Use

  • "I want to contribute to [repo]"
  • "I found a gap in [project]'s documentation"
  • "Submit a PR to [repo]"
  • "Publish this article to Dev.to"
  • "Share this across platforms"
  • "I want to contribute and write about it"
  • "Distribute my skill to HermesHub"

Procedure

Phase 1: Discover

  1. Check repo activity: git log --oneline -20 or check GitHub Insights
  2. Find the gap — scan issues, outdated pages, missing content
  3. Read CONTRIBUTING.md and templates
  4. Study 3-5 existing pages to match style

Phase 2: Scope

  1. Confirm you're adding something distinct (not duplicating)
  2. Pick the right contribution type:
    • Watchlist entry — track a project
    • Capability update — focused addition
    • Example — workflow scenario
    • Setup guide — verified instructions
    • Core profile — full solution profile
  3. For core profiles, plan all required files upfront

Phase 3: Write

  1. Use the repo's template exactly
  2. Write factual, sourced content — no guessing
  3. Include concrete examples with input/output
  4. Document pitfalls and verification steps
  5. Run grep -n '^||' file.md to catch double-pipe markdown issues

Phase 4: Submit

  1. git checkout -b add-<name>
  2. Commit with descriptive messages
  3. gh pr create --repo <upstream> --head <fork>:add-<name>
  4. PR body: what's new, what's updated, verification evidence

Phase 5: Publish (optional)

After merging, share your work:

# Publish article to Dev.to
python3 ~/.hermes/scripts/platform_picker.py publish --file article.md --platform devto

# Cross-post to multiple platforms
python3 ~/.hermes/scripts/platform_picker.py publish --file article.md --platform devto --platform linkedin

# Check what's configured
python3 ~/.hermes/scripts/platform_picker.py status

Platform picker setup (one-time):

python3 ~/.hermes/scripts/platform_picker.py setup devto --api-key YOUR_KEY
python3 ~/.hermes/scripts/platform_picker.py setup github --token YOUR_PAT

Supported platforms: Dev.to (articles), GitHub (gists), LinkedIn (posts), HermesHub (skills via web).

For detailed platform docs, see references/platform-picker.md.

Examples

Example 1: Contribute a solution profile

Input: "Contribute my Hermes+Obsidian+Honcho stack to awesome-second-brain"
Steps:
1. Fork repo, read CONTRIBUTING.md + templates
2. Study 5 existing profiles
3. Write solutions/hermes-obsidian-honcho.md
4. Update README, capability-matrix, solution-layers
5. Open PR with verification evidence

Example 2: Publish an article

Input: "Publish my contribution article to Dev.to"
Steps:
1. Write article.md with YAML frontmatter (title, tags)
2. python3 platform_picker.py publish --file article.md --platform devto
3. Verify URL returned and article is live

Example 3: Cross-post after merging

Input: "Share this on Dev.to and LinkedIn"
Steps:
1. Write one markdown file with frontmatter
2. python3 platform_picker.py publish --file article.md --platform devto --platform linkedin
3. Verify both URLs

Pitfalls

  • Double-pipe markdown — bulk patching introduces ||. Verify with grep.
  • Stream timeouts — files >100 lines need Python (execute_code), not write_file
  • Guessing commands — test all setup steps against live deployment
  • Scope creep — one contribution per PR
  • Missing cross-references — profile pages need links to comparison pages
  • Wrong format — each repo has its own SKILL.md format. Match existing style.
  • Forgetting allowed-tools — HermesHub requires declared tool access

Verification

  • PR opened with evidence of testing
  • No hardcoded credentials in any files
  • All commands tested against live deployment
  • Cross-references added to comparison/index pages
  • Markdown renders correctly (no ||)
  • If published: article URL is live and correct

Sources

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