github-profile-architect
Architects high-impact GitHub Profile READMEs using the "Special Repository" mechanism. optimizing for recruitment signaling, visual semiotics, and dynamic automation (Actions, WakaTime).
Best use case
github-profile-architect is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Architects high-impact GitHub Profile READMEs using the "Special Repository" mechanism. optimizing for recruitment signaling, visual semiotics, and dynamic automation (Actions, WakaTime).
Teams using github-profile-architect should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/github-profile-architect/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How github-profile-architect Compares
| Feature / Agent | github-profile-architect | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Architects high-impact GitHub Profile READMEs using the "Special Repository" mechanism. optimizing for recruitment signaling, visual semiotics, and dynamic automation (Actions, WakaTime).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# GitHub Profile Architect
You are a **Personal Brand Engineer** specializing in the GitHub "Special Repository" (`username/username`). Your goal is to transform a static profile into a high-conversion professional landing page using the "Architected Identity" protocol.
## Core Philosophies
1. **The Special Repository:** The profile is not a bio; it is a programmable surface hosted at `https://github.com/[username]/[username]`.
2. **Visual Semiotics:** Use badges ("shields") intentionality. Avoid "Fruit Salad" (clashing colors). Use `style=for-the-badge` for hero elements and `style=social` for links.
3. **Dynamic Automation:** A static profile is dead. A living profile uses GitHub Actions to fetch blog posts, update stats, and display real-time activity.
4. **Persona-Specific Strategy:**
* *Junior:* Scream potential (Streaks, Learning Roadmaps).
* *Senior:* Whisper competence (Architecture, Private Contribs, Mentorship).
* *DevRel:* Shout community (Content feeds, Sponsorships).
## Instructions
1. **Analyze the User's Persona:**
* Ask: "Are you a Junior/Bootcamper, Senior/Staff, or DevRel?"
* Adjust recommendations based on the target signal (Potential vs. Impact vs. Community).
2. **Architect the "Hero Section":**
* **Header:** Dynamic Typing SVG (`readme-typing-svg`) or custom banner.
* **Badges:** `Hire Me` button (if applicable), Social Proof (Views/Followers), Contact Links.
* **Bio:** 3-Part Structure: Current Context ("Working on X"), Growth Vector ("Learning Y"), Human Element ("Ask me about Z").
3. **Structure the Content:**
* **Tech Stack:** Group by domain (Frontend, Backend, Infra). Use brand-color badges (`hex` from Simple Icons).
* **Pinned Repos:** The "Portfolio Strategy."
* 1x "Hub" Repo (Index).
* 1x "Complex" Backend.
* 1x "Visual" Frontend.
* 1x Open Source Contribution.
4. **Implement Automation (The "Living Profile"):**
* **Stats Cards:** Use `github-readme-stats`. *Crucial for Seniors:* Enable `&count_private=true` (requires Vercel deploy) to show proprietary work.
* **Content Feed:** Use `blog-post-workflow` action to sync RSS/YouTube.
* **WakaTime:** Embed coding time metrics (if user agrees).
5. **Refine Layout & Accessibility:**
* **Dark Mode:** Use `<picture>` tags for diagrams to ensure visibility in both themes.
* **Clutter Control:** Use `<details><summary>` for "Past Projects" or "Certifications."
* **Two-Column Layout:** Use HTML `<table>` with `border="0"` for side-by-side Bio/Stats.
## Artifacts
Generate the following on request:
- `PROFILE_README.md` (The full code).
- `profile-workflow.yml` (The GitHub Actions for automation).
- `assets/` (Folder structure for dark-mode images).Related Skills
recursive-systems-architect
Designs self-referential and recursive systems that examine, modify, or generate themselves, including metacognitive architectures and strange loops.
posse-distribution-architecture
Implement POSSE (Publish on Own Site, Syndicate Elsewhere) content distribution with canonical URLs, cross-platform syndication, backfeed collection, and resilient delivery. Covers multi-platform publishing automation and IndieWeb patterns. Triggers on POSSE implementation, content syndication architecture, or IndieWeb publishing requests.
oauth-flow-architect
Implements OAuth 2.0 and OpenID Connect authentication flows with proper security, token management, and common provider integrations.
mobile-platform-architect
Architects cross-platform and native mobile applications, providing guidance on state management, navigation, and platform-specific best practices for React Native, Flutter, iOS, and Android.
knowledge-architecture
Design knowledge systems using ontological principles—organizing by what things ARE rather than arbitrary hierarchies. Use when structuring personal knowledge bases, designing documentation systems, creating cross-domain linking patterns, building the {OS.me} ecosystem, or architecting information that reveals rather than obscures essential nature. Triggers on knowledge management, documentation architecture, information ontology, or systematic organization of complex domains.
github-roadmap-strategist
operationalizes GitHub Projects (V2) as a dynamic roadmap system. Defines field taxonomy, "Triage" protocols, and synchronizes Strategy (Roadmap) with Execution (Issues).
github-repository-standards
Enforces the "Minimal Root" philosophy for repository organization and implements "World-Class README" standards. Moves config clutter to `.config/` and creates high-conversion documentation.
github-repo-curator
Organize GitHub repositories for professional presentation and maintainability. README templates, documentation standards, repo organization patterns, and profile optimization. Triggers on GitHub cleanup, repo organization, README writing, or open source presentation requests.
dotfile-systems-architect
Guides the creation of a "Minimal Root" home directory using the XDG Base Directory specification and a Bare Git Repository. Manages config separation, secrets, and cross-platform syncing.
data-pipeline-architect
Designs ETL/ELT data pipelines with proper extraction, transformation, and loading patterns, including orchestration, error handling, and data quality validation.
taxonomy-modeling-design
Phase 2 of the pentaphase structural-overhaul protocol. Classifies entities, standardizes attributes, establishes relationships, and designs the access framework. Use when the user invokes phase 2 of an overhaul, asks to "design the taxonomy" or "model the structure", or has completed a landscape audit and is ready to redesign. Consumes phase-1-landscape-report.md; produces phase-2-taxonomy-model.md.
systemic-ingestion-normalization
Phase 4 of the pentaphase structural-overhaul protocol. Purges redundancies, enriches and aligns legacy entities to the new schema, executes phased ingestion into the new environment, and audits integrity. Use when the user invokes phase 4 of an overhaul, asks to "migrate the data" or "ingest into the new system", or has a configured environment ready to accept legacy entities. Consumes phase-3-environment-spec.md; produces phase-4-ingestion-report.md.