github-profile

Name: github-profile
Author: jdevalk

85stars9forks

How to install github-profile?

jdevalk/skills/github-profile

$npx -y skills add jdevalk/skills --skill github-profile

Installs into the current project.

Summary

Audits and optimizes GitHub profile pages — profile README, metadata fields, pinned repositories, stats widgets, and contribution visibility. Use this skill whenever the user asks to improve, create, review, or optimize their GitHub profile, or mentions "profile README", "GitHub

Files · 1

View on GitHub

SKILL.md

1	# GitHub Profile Optimizer
2
3	This skill audits a GitHub profile and generates an optimized profile README along with recommendations for metadata, pinned repositories, and stats widgets. A strong GitHub profile is a developer's storefront — it shapes perception before anyone reads a line of code.
4
5	Code recipes live in `AGENTS.md` — read it when you need to implement a specific fix. This file has the workflow and audit checklist.
6
7	## Workflow
8
9	1. Gather profile context — Understand who this person/org is and what they want to showcase
10	2. Audit the current profile — Score every element of the profile's public presence
11	3. Generate the profile README — Write a polished, scannable README.md
12	4. Recommend metadata and configuration — Advise on bio, pinned repos, settings, and widgets
13	5. Verify — Confirm rendering, badge URLs, and summarize next steps
14
15	---
16
17	## Phase 0: Gather Context
18
19	### Determine profile type
20
21	Ask the user (if not obvious): is this a personal profile or an organization profile? The mechanics differ significantly:
22
23	\| Feature \| Personal profile \| Organization profile \|
24	\| --- \| --- \| --- \|
25	\| README location \| `username/username/README.md` \| `.github/profile/README.md` \|
26	\| Visibility options \| Public only \| Public + member-only (via `.github-private` repo) \|
27	\| Pinned repos \| Up to 6 \| Up to 6 public + 6 member-only \|
28	\| Contribution graph \| Yes \| No \|
29	\| Achievements \| Yes \| No \|
30
31	### Collect information
32
33	Gather before writing: username, current role/company, primary technologies, what they want to showcase, tone (professional/casual/creative/minimal), and target audience (recruiters/collaborators/investors/OSS community).
34
35	If `gh` is available (`gh auth status`), pull automatically:
36
37	- `gh api user` — name, bio, company, location, blog, twitter
38	- `gh api users/{username}/repos?sort=stars&per_page=10` — top repos for pin recommendations
39	- `gh repo view {username}/{username} --json name 2>/dev/null` — check if magic repo exists
40
41	---
42
43	## Phase 1: Audit
44
45	If the user has an existing profile, audit it. If they're starting fresh, skip to Phase 2. Score four categories (each x/10, total x/40):
46
47	### Profile README (x/10)
48
49	- Exists? No `username/username` repo with README.md is the biggest miss.
50	- Structure — Ideal flow: greeting/identity → current work → tech stack (badges) → GitHub stats → featured projects → social links → personal touch.
51	- Length — 400-800 words. Under 200 feels thin; over 2,000 clutters.
52	- Scannability — Gist in 10 seconds? Use `<details>` for collapsible sections.
53	- Freshness — Dynamic content still updating? GitHub stops cron Actions after 60 days of repo inactivity.
54
55	### Profile Metadata (x/10)
56
57	Every empty field is a missed opportunity:
58
59	- Photo — clear headshot, consistent across platforms?
60	- Bio — filled in (160 char limit), states role + primary tech + distinguishing trait?
61	- Company — linked with `@` prefix? Location, Website — filled in?
62	- Social accounts — Twitter/X, LinkedIn linked? Cross-linking builds trust.
63	- Pronouns — signals inclusivity. Status — shows current work or availability?
64
65	### Pinned Repositories (x/10)
66
67	Up to 6 repos (including contributed-to repos):
68
69	- All 6 slots used? Descriptions filled in? Variety across technologies?
70	- Prioritize repos with stars (social proof) that align with career/business goals.
71	- Each pinned repo should have a polished README (github-repo skill applies here).
72
73	### Contribution Activity (x/10)
74
75	- Graph — reasonably active? Completely empty raises questions.
76	- Private contributions — "Include private contributions" enabled in settings?
77	- Achievements — Starstruck, Pull Shark, Arctic Code Vault Contributor add credibility.
78
79	---
80
81	## Phase 2: Generate the Profile README
82
83	Based on the audit (or from scratch), produce the profile README. Read `AGENTS.md` for detailed recipes.
84
85	The profile README should be scannable, personal, and purposeful — every section should serve the person's goals. Adapt tone and structure to the audience.
86
87	`AGENTS.md` sections: Personal profile README template, Stats widgets, Badges for tech stack and social links, Dynamic auto-updating content, Organization profile README, Profile generators.
88
89	---
90
91	## Phase 2.5: Metadata and readability pass
92
93	1. **`

People who liked this also viewed

6 picks

Type

github-profile

85stars9forks

View on GitHub

How to install github-profile?

jdevalk/skills/github-profile

$npx -y skills add jdevalk/skills --skill github-profile

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# GitHub Profile Optimizer
2
3	This skill audits a GitHub profile and generates an optimized profile README along with recommendations for metadata, pinned repositories, and stats widgets. A strong GitHub profile is a developer's storefront — it shapes perception before anyone reads a line of code.
4
5	Code recipes live in `AGENTS.md` — read it when you need to implement a specific fix. This file has the workflow and audit checklist.
6
7	## Workflow
8
9	1. Gather profile context — Understand who this person/org is and what they want to showcase
10	2. Audit the current profile — Score every element of the profile's public presence
11	3. Generate the profile README — Write a polished, scannable README.md
12	4. Recommend metadata and configuration — Advise on bio, pinned repos, settings, and widgets
13	5. Verify — Confirm rendering, badge URLs, and summarize next steps
14
15	---
16
17	## Phase 0: Gather Context
18
19	### Determine profile type
20
21	Ask the user (if not obvious): is this a personal profile or an organization profile? The mechanics differ significantly:
22
23	\| Feature \| Personal profile \| Organization profile \|
24	\| --- \| --- \| --- \|
25	\| README location \| `username/username/README.md` \| `.github/profile/README.md` \|
26	\| Visibility options \| Public only \| Public + member-only (via `.github-private` repo) \|
27	\| Pinned repos \| Up to 6 \| Up to 6 public + 6 member-only \|
28	\| Contribution graph \| Yes \| No \|
29	\| Achievements \| Yes \| No \|
30
31	### Collect information
32
33	Gather before writing: username, current role/company, primary technologies, what they want to showcase, tone (professional/casual/creative/minimal), and target audience (recruiters/collaborators/investors/OSS community).
34
35	If `gh` is available (`gh auth status`), pull automatically:
36
37	- `gh api user` — name, bio, company, location, blog, twitter
38	- `gh api users/{username}/repos?sort=stars&per_page=10` — top repos for pin recommendations
39	- `gh repo view {username}/{username} --json name 2>/dev/null` — check if magic repo exists
40
41	---
42
43	## Phase 1: Audit
44
45	If the user has an existing profile, audit it. If they're starting fresh, skip to Phase 2. Score four categories (each x/10, total x/40):
46
47	### Profile README (x/10)
48
49	- Exists? No `username/username` repo with README.md is the biggest miss.
50	- Structure — Ideal flow: greeting/identity → current work → tech stack (badges) → GitHub stats → featured projects → social links → personal touch.
51	- Length — 400-800 words. Under 200 feels thin; over 2,000 clutters.
52	- Scannability — Gist in 10 seconds? Use `<details>` for collapsible sections.
53	- Freshness — Dynamic content still updating? GitHub stops cron Actions after 60 days of repo inactivity.
54
55	### Profile Metadata (x/10)
56
57	Every empty field is a missed opportunity:
58
59	- Photo — clear headshot, consistent across platforms?
60	- Bio — filled in (160 char limit), states role + primary tech + distinguishing trait?
61	- Company — linked with `@` prefix? Location, Website — filled in?
62	- Social accounts — Twitter/X, LinkedIn linked? Cross-linking builds trust.
63	- Pronouns — signals inclusivity. Status — shows current work or availability?
64
65	### Pinned Repositories (x/10)
66
67	Up to 6 repos (including contributed-to repos):
68
69	- All 6 slots used? Descriptions filled in? Variety across technologies?
70	- Prioritize repos with stars (social proof) that align with career/business goals.
71	- Each pinned repo should have a polished README (github-repo skill applies here).
72
73	### Contribution Activity (x/10)
74
75	- Graph — reasonably active? Completely empty raises questions.
76	- Private contributions — "Include private contributions" enabled in settings?
77	- Achievements — Starstruck, Pull Shark, Arctic Code Vault Contributor add credibility.
78
79	---
80
81	## Phase 2: Generate the Profile README
82
83	Based on the audit (or from scratch), produce the profile README. Read `AGENTS.md` for detailed recipes.
84
85	The profile README should be scannable, personal, and purposeful — every section should serve the person's goals. Adapt tone and structure to the audience.
86
87	`AGENTS.md` sections: Personal profile README template, Stats widgets, Badges for tech stack and social links, Dynamic auto-updating content, Organization profile README, Profile generators.
88
89	---
90
91	## Phase 2.5: Metadata and readability pass
92
93	1. **`

People who liked this also viewed

6 picks

Type