Explore skills

Write GitHub profile bios, project README intros, and technical-lab positioning that honestly distinguishes personal experiments from professional experience while making the builder identity clear.

Create strong Proof-Promise-Plan openings for articles, landing pages, README files, LinkedIn posts, videos, and guides.

Design personal websites, portfolios, landing pages, and README hubs around what the reader can gain, not around generic sections like Blog, Projects, and Resume.

Use when a user wants to turn Career Positioning OS resume content into a RenderCV YAML file, install or use the external RenderCV agent skill, or render a resume/CV PDF without reimplementing RenderCV's schema, CLI, themes, or PDF generation.

Rewrite GitHub repository names, About descriptions, README intros, and website tool cards so they communicate practical user value.

Turn an article, video, repository, product, job post, service, or offer into a high-attention value unit: title/headline, thumbnail or visual concept, curiosity gap, proof, and sequential hook. Use when the user wants clickable titles, article thumbnails, project thumbnails, repo/social preview images, hooks, offer framing, or a generalizable value-communication critique.

Generate visual concepts and image prompts for profile banners, article headers, thumbnails, and wallpapers using current-state, desired-state, and transformation-mechanism storytelling.

Core principles for technical communication such as commits, PR descriptions, branch names, and technical documentation. Use when writing or refining engineering-facing messaging and when other skills need a shared communication baseline.

Mandatory credential protection skill for all agents. Prevents reading, exposing, or leaking credentials, secrets, API keys, tokens, passwords, and auth-capable config files.

Analyze the current conversation or mine historical chat sessions for correction patterns, wrong conclusions, or unnecessary user intervention. Use when the user wants to improve prompts, skills, workflows, or guardrails based on repeated mistakes.

Guide for working through a Jira story efficiently by separating context gathering, immutable evidence collection, codebase exploration, human-in-the-loop specification refinement, execution planning, and implementation. Use when turning a ticket into a reliable engineering workflow instead of jumping straight to code.

Creates CLAUDE.md/AGENTS.md from the harness template (if absent) and configures docs/agents/ so harness skills know the issue tracker, triage labels, domain docs, GitHub Project board, and session state location. Run before first use of triage, to-prd, to-issues, context-handover, or session-start — or if those skills appear to be missing context. Typically consumes <30% of a context window.