Agent skill

GitHub Presence

by sickn33 in sickn33/agentic-awesome-skills

When the user wants to optimize their GitHub profile, README, or project discoverability.

MITAuto-check passedDevelopment

Install GitHub Presence

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill github-presence -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills github-presence --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/github-presence .claude/skills/github-presence && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
github-presence
GitHub stars
47k
Used in
1 other repo
Token cost
~3.4k tokens
SKILL.md length
837 words
Files
2
Skills in repo
1,354
Repo updated
First seen
Licence
MIT

At a glance

When the user wants to optimize their GitHub profile, README, or project discoverability.

  • Works in 3 steps: Read… → Audit your current GitHub presence… → Understand: GitHub is often the first…
  • Wants to optimize their GitHub profile
  • SKILL.md covers When to Use, Before You Start, README Structure and Installation, plus 8 more sections
  • Calls npm, yarn and pnpm; reaches github.com and img.shields.io; needs METRICS_TOKEN and TWITTER_CONSUMER_KEY

What it does

GitHub Presence is an agent skill from sickn33/agentic-awesome-skills. When the user wants to optimize their GitHub profile, README, or project discoverability. Trigger phrases include "GitHub README," "README optimization," "GitHub profile," "GitHub stars," "GitHub discoverability," "awesome lists," or "GitHub marketing."

Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).

It sits in Development, covering Technical documentation. It works with GitHub. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Wants to optimize their GitHub profile
  • Project discoverability
  • Phrases include GitHub README
  • README optimization

Example prompts

  • “GitHub README,”
  • “README optimization,”
  • “GitHub profile,”
  • “/github-presence”

Requirements

  • Node.js
  • A credential in METRICS_TOKEN
  • A credential in TWITTER_CONSUMER_KEY

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Read .agents/developer-audience-context.md if it exists
  2. Audit your current GitHub presence (profile, pinned repos, READMEs)
  3. Understand: GitHub is often the first technical evaluation — optimize accordingly

What it can do on your machine

Read from SKILL.md and the folder at commit ec02547. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • yarn
    • pnpm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com
    • img.shields.io
    • npmjs.com
    • discord.gg
    • twitter.com
    • linkedin.com
    • github-readme-stats.vercel.app
    • buymeacoffee.com

    Also links to:

    • octolens.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • METRICS_TOKEN
    • TWITTER_CONSUMER_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

GitHub Presence loads about 3.4k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 837 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~67
When it runs · the whole SKILL.md, loaded when a task matches
~3.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit ec02547, republished under its MIT licence (© sickn33). 837 words, ~3,434 tokens.

Download SKILL.mdSave it as .claude/skills/github-presence/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
github-presence
description
When the user wants to optimize their GitHub profile, README, or project discoverability. Trigger phrases include "GitHub README," "README optimization," "GitHub profile," "GitHub stars," "GitHub discoverability," "awesome lists," or "GitHub marketing."
risk
critical
source
https://github.com/jonathimer/devmarketing-skills/tree/main/skills/github-presence
source_repo
jonathimer/devmarketing-skills
source_type
community
date_added
2026-07-01
license
MIT
license_source
https://github.com/jonathimer/devmarketing-skills/blob/main/LICENSE

GitHub Presence

When to Use

Use this skill when you need when the user wants to optimize their GitHub profile, README, or project discoverability. Trigger phrases include "GitHub README," "README optimization," "GitHub profile," "GitHub stars," "GitHub discoverability," "awesome lists," or "GitHub marketing.".

GitHub is where developers evaluate your project before trying it. This skill covers README optimization, profile READMEs, discoverability through topics and awesome lists, and using GitHub features for marketing.


Before You Start

  1. Read .agents/developer-audience-context.md if it exists
  2. Audit your current GitHub presence (profile, pinned repos, READMEs)
  3. Understand: GitHub is often the first technical evaluation — optimize accordingly

README Structure

The Anatomy of a Great README
SectionPurposeRequired?
Logo/BannerBrand recognition, visual appealRecommended
BadgesQuick trust signals, statusRecommended
One-linerWhat it does in one sentenceRequired
Hero exampleImmediate "what does it look like?"Highly recommended
FeaturesWhy use this over alternativesRequired
Quick startGet running in < 2 minutesRequired
InstallationAll installation methodsRequired
UsageCore usage examplesRequired
DocumentationLink to full docsRequired
ContributingHow to contributeRecommended
LicenseLegal clarityRequired
README Template
markdown
<div align="center">
  <img src="logo.svg" alt="Project Name" width="200">
  <h1>Project Name</h1>
  <p><strong>One compelling sentence explaining what this does.</strong></p>

  <!-- Badges -->
  <a href="https://github.com/org/repo/actions"><img src="https://github.com/org/repo/workflows/CI/badge.svg" alt="CI"></a>
  <a href="https://www.npmjs.com/package/name"><img src="https://img.shields.io/npm/v/name.svg" alt="npm version"></a>
  <a href="https://github.com/org/repo/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue.svg" alt="License"></a>
  <a href="https://discord.gg/invite"><img src="https://img.shields.io/discord/123456789" alt="Discord"></a>

  <br>
  <br>

  <a href="https://docs.example.com">Documentation</a> •
  <a href="https://example.com">Website</a> •
  <a href="https://discord.gg/invite">Discord</a>
</div>

---

## Why Project Name?

- **Feature 1** — Brief explanation
- **Feature 2** — Brief explanation
- **Feature 3** — Brief explanation

## Quick Start

```bash
npm install project-name
javascript
import { thing } from 'project-name';

const result = thing.doSomething();
console.log(result);

Installation

npm
bash
npm install project-name
yarn
bash
yarn add project-name
pnpm
bash
pnpm add project-name

Usage

Basic Example
javascript
// Code example with comments
Advanced Example
javascript
// More complex example

Documentation

Full documentation available at docs.example.com

Contributing

We welcome contributions! Please see CONTRIBUTING.md for details.

License

MIT © Your Name


---

## Badges That Matter

### Trust Signal Badges

| Badge | What it shows | When to use |
|-------|--------------|-------------|
| CI/Build status | Code quality | Always |
| Version | Latest release | Always for packages |
| License | Legal clarity | Always |
| Downloads/installs | Adoption | When impressive |
| Coverage | Test quality | If > 70% |
| Security | Audit status | If you have it |

### Community Badges

| Badge | Source | Purpose |
|-------|--------|---------|
| Discord members | shields.io | Show active community |
| GitHub stars | shields.io | Social proof |
| Contributors | shields.io | Open source health |
| Last commit | shields.io | Project activity |

### Badge Services

| Service | URL | Best for |
|---------|-----|----------|
| Shields.io | shields.io | Most badges |
| Badgen | badgen.net | Fast, minimal |
| GitHub badges | Native | Actions, issues |

### Badge Examples

```markdown
<!-- Build status -->
![CI](https://github.com/org/repo/workflows/CI/badge.svg)

<!-- npm version -->
[![npm](https://img.shields.io/npm/v/package-name.svg)](https://www.npmjs.com/package/package-name)

<!-- Downloads -->
[![Downloads](https://img.shields.io/npm/dm/package-name.svg)](https://www.npmjs.com/package/package-name)

<!-- License -->
[![License](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)

<!-- Discord -->
[![Discord](https://img.shields.io/discord/SERVER_ID?color=7289da&logo=discord&logoColor=white)](https://discord.gg/invite)

<!-- Stars -->
[![GitHub stars](https://img.shields.io/github/stars/org/repo?style=social)](https://github.com/org/repo)

Profile README

Setting Up Profile README
  1. Create a repository with your username (e.g., github.com/yourname/yourname)
  2. Add a README.md file
  3. This displays on your profile page
Profile README Structure
markdown
# Hi, I'm [Name] 👋

[One sentence about what you do]

## What I'm Working On

- 🔭 Building [project] — [brief description]
- 🌱 Learning [technology]
- 💬 Ask me about [expertise areas]

## Projects

| Project | Description | Stars |
|---------|-------------|-------|
| [Project 1](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/github-presence/link) | Brief description | ![Stars](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/github-presence/badge) |
| [Project 2](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/github-presence/link) | Brief description | ![Stars](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/github-presence/badge) |

## Recent Blog Posts

<!-- BLOG-POST-LIST:START -->
<!-- Automated with GitHub Actions -->
<!-- BLOG-POST-LIST:END -->

## Connect

[![Twitter](https://img.shields.io/badge/-Twitter-1DA1F2?style=flat&logo=twitter&logoColor=white)](https://twitter.com/handle)
[![LinkedIn](https://img.shields.io/badge/-LinkedIn-0077B5?style=flat&logo=linkedin&logoColor=white)](https://linkedin.com/in/handle)

## GitHub Stats

![Your GitHub stats](https://github-readme-stats.vercel.app/api?username=yourusername&show_icons=true)
Profile README Best Practices
DoDon't
Keep it scannableWrite paragraphs
Show your best projectsList everything
Include current workLet it get stale
Add contact methodsMake it hard to reach you
Show personalityBe generic

Discoverability

GitHub Topics

Topics are how people find repositories. Optimize for search.

Topic strategyExample
Technologyjavascript, rust, python
Frameworkreact, nextjs, django
Use casecli, api, testing
Categorydeveloper-tools, devops
Problemauthentication, caching

Add topics: Repository settings → Topics (up to 20)

Search Optimization

GitHub search considers:

  1. Repository name — Include main keyword
  2. Description — 350 chars, keyword-rich
  3. README content — Full text indexed
  4. Topics — Category matching
  5. Language — Auto-detected
Awesome Lists

Getting on awesome lists drives traffic and credibility.

StepAction
1Find relevant awesome lists (search "awesome + [topic]")
2Check list requirements (quality, activity, docs)
3Ensure your project meets criteria
4Submit PR following list's guidelines
5Be patient — curation takes time

Popular awesome lists for dev tools:

  • awesome-cli-apps
  • awesome-selfhosted
  • awesome-nodejs
  • awesome-python
  • awesome-go
  • awesome-rust
  • awesome-devops

GitHub Actions for Marketing

Automated README Updates
yaml
# .github/workflows/readme-update.yml
name: Update README

on:
  schedule:
    - cron: '0 0 * * *'  # Daily
  workflow_dispatch:

jobs:
  update:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      # Example: Update blog post list
      - uses: gautamkrishnar/blog-post-workflow@master
        with:
          feed_list: "https://yourblog.com/feed"

      - name: Commit changes
        run: |
          git config --local user.email "action@github.com"
          git config --local user.name "GitHub Action"
          git add -A
          git diff --quiet && git diff --staged --quiet || git commit -m "Update README"
          git push
Metrics and Stats
yaml
# Auto-update GitHub stats image
- uses: lowlighter/metrics@latest
  with:
    token: ${{ secrets.METRICS_TOKEN }}
    filename: github-metrics.svg
Release Announcements
yaml
# Tweet on new release
name: Release Announcement
on:
  release:
    types: [published]

jobs:
  announce:
    runs-on: ubuntu-latest
    steps:
      - name: Tweet
        uses: ethomson/send-tweet-action@v1
        with:
          status: "🚀 ${{ github.repository }} ${{ github.event.release.tag_name }} released! ${{ github.event.release.html_url }}"
          consumer-key: ${{ secrets.TWITTER_CONSUMER_KEY }}
          # ... other secrets

GitHub Sponsors

Setting Up Sponsors
  1. Join GitHub Sponsors (github.com/sponsors)
  2. Create compelling tier descriptions
  3. Set up funding.yml in repos

funding.yml example:

yaml
github: [yourusername]
patreon: yourpatreon
open_collective: yourproject
ko_fi: yourkofi
custom: ["https://buymeacoffee.com/you"]
Sponsor Tiers That Work
TierPriceOffer
Supporter$5/moThanks + name in README
Backer$15/moLogo in README + Discord role
Sponsor$50/moPriority support + feature voting
Enterprise$200+/moDedicated support + consultation

Platform-Specific Do's and Don'ts

Show full SKILL.md (354 more words)Show less
Do's
  1. Do optimize your README for first impression
  2. Do use badges for quick trust signals
  3. Do add relevant topics (up to 20)
  4. Do keep your profile README current
  5. Do respond to issues and PRs promptly
  6. Do pin your best repositories
  7. Do include clear installation instructions
  8. Do submit to relevant awesome lists
Don'ts
  1. Don't neglect the README — it's your landing page
  2. Don't use too many badges (cluttered)
  3. Don't let issues pile up unanswered
  4. Don't forget a license file
  5. Don't use low-quality or broken images
  6. Don't write walls of text without structure
  7. Don't ignore contribution guidelines

Measuring Success

GitHub Metrics to Track
MetricWhat it tells youGoal
StarsInterest/bookmarksGrowth over time
ForksActive usageQuality > quantity
ClonesPeople trying itPre-install interest
TrafficProfile/repo viewsAwareness
ReferrersWhere traffic comes fromChannel effectiveness
ContributorsCommunity healthSustainable project
Traffic Insights

Access via: Repository → Insights → Traffic

  • Views and unique visitors
  • Popular content (which files)
  • Referring sites
  • Clone activity

Tools

ToolUse case
OctolensMonitor GitHub for mentions of your project, competitors, and relevant discussions. Get alerts when people talk about problems you solve.
Shields.ioGenerate status badges
GitHub Readme StatsDynamic stats for profile
CarbonBeautiful code screenshots
readme.soREADME generator
MetricsAdvanced profile stats

README Audit Checklist

  • Clear, keyword-rich name and description
  • Badges show CI status, version, license
  • One-liner explains what it does
  • Quick start gets users running in < 2 min
  • Code examples are copy-pasteable
  • All links work and are HTTPS
  • Images have alt text
  • Mobile-readable formatting
  • License file present
  • Contributing guidelines exist
  • Topics are set (up to 20)
  • Social preview image uploaded

  • developer-audience-context — Know who evaluates your repo
  • hacker-news-strategy — HN users check GitHub before upvoting
  • reddit-engagement — Redditors evaluate via GitHub
  • dev-to-hashnode — Link from README to content

Limitations

  • Use this skill only when the task clearly matches its upstream source and local project context.
  • Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
  • Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/github-presence of sickn33/agentic-awesome-skills.

  • SKILL.md
  • README.md

Open the folder on GitHubat commit ec02547

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

GitHub Presence next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

GitHub Presence compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
GitHub Presence this skillsickn33/agentic-awesome-skills47k1 repos~3.4kAutomated safety check: PassMIT
Update .NET OS Packagesdotnet/core22k—~2.3kAutomated safety check: PassMIT
Beautify GitHub Readmeoil-oil/beautify-github-readme1.8k—~4.1kAutomated safety check: PassMIT
Library Documentation Seekerwithkynam/vibecode-pro-max-kit1.1k2 repos~1kAutomated safety check: NotesMIT
Update .NET Supported OS Matrixdotnet/core22k—~4.1kAutomated safety check: PassMIT
Debate ReviewamElnagdy/review-skills1322 repos~986Automated safety check: PassMIT

Similar skills

  • Official

    Audits and updates os-packages.json files listing the Linux packages each .NET release needs per distro, then regenerates the Markdown from the JSON.

    22k GitHub stars~2.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Beautify GitHub Readme

    oil-oil/beautify-github-readme

    Redesign GitHub README homepages or create project-native pure SVG, hybrid SVG-composed PNG/WebP, and opt-in animated GIF assets.

    1.8k GitHub stars~4.1k tokensUpdated 3 days ago
    DevelopmentAuto-check passed
  • Library Documentation Seeker

    withkynam/vibecode-pro-max-kit

    Looks up library and framework documentation through Context7 first, with bundled Node scripts as a fallback that fetch and analyze llms.txt files.

    1.1k GitHub starsUsed in 2 repos~1k tokens
    DevelopmentAuto-check: notes
  • Official

    Audits and updates the supported-os.json files for .NET releases, checking them against upstream lifecycle data and regenerating the markdown with the release-notes tool.

    22k GitHub stars~4.1k tokensUpdated today
    DevelopmentAuto-check passed
  • Debate Review

    amElnagdy/review-skills

    Two-model debate review of a GitHub PR, GitLab MR, Azure DevOps PR, or local working tree, posted as inline comments or printed.

    132 GitHub starsUsed in 2 repos~986 tokens
    DevelopmentAuto-check passed
  • Post Draft Review

    agent-substrate/substrate

    Posts pull request review findings as GitHub draft (pending) inline comments for a human to edit and submit, instead of publishing them straight to the PR author.

    4.5k GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,354 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed
  • Content Creator

    sickn33/agentic-awesome-skills

    Drafts and reviews audience-specific content from supplied brand examples, with local scripts for brand voice and SEO diagnostics, channel templates and a content calendar.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

Works with

Categories

Questions about GitHub Presence

What does GitHub Presence do?

When the user wants to optimize their GitHub profile, README, or project discoverability. GitHub Presence is an agent skill from sickn33/agentic-awesome-skills. When the user wants to optimize their GitHub profile, README, or project discoverability.

When should I use GitHub Presence?

GitHub Presence fits situations like: wants to optimize their GitHub profile; project discoverability; phrases include GitHub README; README optimization.

How do I install GitHub Presence in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill github-presence -a claude-code`. Or copy the skill folder (skills/github-presence in sickn33/agentic-awesome-skills) into .claude/skills/github-presence in your project. Claude Code loads it when a task matches its description.

How do I install GitHub Presence in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill github-presence -a codex`. Or copy the skill folder (skills/github-presence in sickn33/agentic-awesome-skills) into .agents/skills/github-presence in your project. Codex loads it when a task matches its description.

Can I use GitHub Presence in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill github-presence -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-presence, .gemini/skills/github-presence, .github/skills/github-presence and .opencode/skills/github-presence in your project.

What does GitHub Presence need to run?

Going by SKILL.md and its folder, GitHub Presence needs the command-line tools its instructions call (npm, yarn and pnpm) and credentials named METRICS_TOKEN and TWITTER_CONSUMER_KEY. Our summary lists: Node.js; A credential in METRICS_TOKEN; A credential in TWITTER_CONSUMER_KEY.

Does GitHub Presence access the network?

SKILL.md names 9 domains. In commands or code: github.com, img.shields.io, npmjs.com, discord.gg, twitter.com, linkedin.com, github-readme-stats.vercel.app and buymeacoffee.com; the agent is likely to contact these when it follows the instructions. As links in the text: octolens.com. This is read from the text; nothing was executed.

Is GitHub Presence safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does GitHub Presence use?

GitHub Presence is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does GitHub Presence use?

About 3.4k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to GitHub Presence?

Skills that share tags, products or a category with GitHub Presence: Update .NET OS Packages (dotnet/core, 22k stars), Beautify GitHub Readme (oil-oil/beautify-github-readme, 1.8k stars), Library Documentation Seeker (withkynam/vibecode-pro-max-kit, 1.1k stars) and Update .NET Supported OS Matrix (dotnet/core, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains GitHub Presence?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,343 GitHub stars. The repository holds 1,354 skills in this directory. The repository was last updated on October 7, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.