# Profile Readme Positioning

> 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.

- Skill: `arthurzakirov/profile-readme-positioning` (Agent Skill)
- Install (CLI): `npx skillmds@latest add arthurzakirov/profile-readme-positioning`
- Raw SKILL.md: https://api.skillmd.com/api/skills/arthurzakirov/profile-readme-positioning/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: ArthurZakirov (https://skillmd.com/u/arthurzakirov)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/arthurzakirov/profile-readme-positioning

---


# Profile README Positioning Skill

## Use this when

Use this skill to write or revise:

- GitHub profile bio
- GitHub profile README
- project README intro
- personal lab positioning
- open-source project description
- portfolio technical project page

## Core principle

A GitHub profile is not the same as a resume.

A resume says:

```text
Here is the business value I created in professional settings.
```

A GitHub profile can say:

```text
Here is the kind of builder I am when nobody assigns me a ticket.
```

## Step 1 — Define the repository/profile mission

Ask:

- What kind of problems does this profile/project solve?
- Are these personal, professional, open-source, educational, or experimental?
- What type of builder does this reveal?
- What should a visitor understand in 5 seconds?
- What should not be overclaimed?

## Step 2 — Choose positioning type

### Personal automation lab

For tools built to solve the creator's own problems.

Template:

```text
Personal automation lab for [domain/tools] and practical systems that reduce [type of friction].
```

### Technical experiments lab

For exploratory projects.

```text
A public lab for experiments in [topics], focused on learning, prototypes, and reusable patterns.
```

### Open-source utility profile

For reusable tools.

```text
Building small, practical tools for [audience/problem], with a focus on [qualities].
```

### Project-specific README

```text
[Project] helps [audience] solve [problem] by [mechanism].
```

## Step 3 — Be honest without self-sabotage

Avoid defensive wording:

```text
This code is not good enough.
This is not representative of professional code.
This is just random personal stuff.
```

Use calibrated wording:

```text
This is a public lab for practical experiments.
These projects prioritize solving real personal workflows quickly.
Some repos are prototypes, others are reusable tools.
```

## Step 4 — Explain what appears here

For a profile README, include:

- what this profile is
- current focus areas
- example categories of work
- philosophy of sharing
- boundaries/disclaimer if needed

## GitHub bio options

Short bios:

```text
Personal automation lab: agentic AI systems, browser agents, workflows, and tools that reduce real-life friction.
```

```text
Building practical tools for high-friction workflows with automation, agents, and browser-based systems.
```

```text
Turning everyday friction into agentic workflows, browser automations, and reusable personal tools.
```

## README skeleton

```markdown
# [Profile / Lab Name]

I use this GitHub as a public lab for [type of tools/projects].

Most projects here explore:

- [topic 1]
- [topic 2]
- [topic 3]
- [topic 4]

The goal:

> If I solve a real problem for myself and the solution might help someone else, I try to make it shareable.

Some projects are polished utilities. Others are experiments, prototypes, or learning artifacts.
```

## Project README intro skeleton

```markdown
# [Project Name]

[Project Name] helps [audience] solve [painful problem] by [mechanism].

It was built because [specific friction].

## What it does

- [capability]
- [capability]
- [capability]

## Why it exists

[Explain the before state and why existing solutions were insufficient.]

## Status

[Prototype / usable / production-ready / experimental]
```

## Quality bar

A strong profile README:

- makes the builder identity clear
- does not pretend personal projects are company work
- does not apologize for being experimental
- explains the theme connecting projects
- helps the visitor decide what to inspect next