agentsclimarketplace

Github research maintainer

Skill StaryMoon/ai-researcher-skills/skills/github-research-maintainer

Practical skill pack for AI research agents: paper briefing, experiment planning, rebuttal drafting, radar maintenance, and GitHub upkeep.

Install
npx -y skills add StaryMoon/ai-researcher-skills --skill github-research-maintainer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, as published. Nobody here has run it

GitHub Research Maintainer

Purpose

Make a research repository credible, discoverable, and easy to evaluate. The skill focuses on README structure, release hygiene, issue/PR handling, honest status language, and GitHub profile presentation.

When To Use

Use this skill when the user wants to publish a research repo, improve a GitHub project, prepare a release, respond to issues, or make a project more attractive to stars and followers without spam.

Inputs

  • Repository path or GitHub URL.
  • Paper link or project goal.
  • Current README, release notes, issues, or PRs.
  • Optional target audience: researcher, student, recruiter, maintainer, or user.

Workflow

  1. Inspect the README first viewport. It must answer what this is, who it is for, and how to try it.
  2. Check repository truthfulness: official vs unofficial, reproduced vs paper-reported, local test coverage, and missing assets.
  3. Check install path, quick start, examples, screenshots, topics, license, citation, and changelog.
  4. Identify one sharp differentiator that is visible above the fold.
  5. Prepare release notes that list user-visible changes, not internal rambling.
  6. If making external PRs, add the project only where it naturally fits and never ask for stars in other projects' issue threads.
  7. End with a small maintainer checklist.

Output

  • First-Viewport Diagnosis
  • Credibility Fixes
  • README Patch Plan
  • Release Checklist
  • Topic Suggestions
  • External PR Fit

Quality Gates

  • Do not misrepresent a project as official.
  • Do not hide unreproduced status when it affects user expectations.
  • Do not spam issues or PRs for promotion.
  • Use precise project descriptions and concrete screenshots or examples whenever possible.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.