ArthurZakirov Tool Positioning for Repositories Skill
Purpose
Rewrite GitHub repository names, About descriptions, README intros, and website tool cards so they communicate practical user value.
Principle
Do not frame repositories as portfolio projects. Frame them as tools the reader can use.
Tool Card Formula
Name -> user benefit -> setup path
Example:
AgentDesk - Make any machine ready for human and AI-agent work. Open the repository and follow the setup guide.
README Intro Formula
This tool helps you [achieve outcome] by [mechanism]. It is useful when [situation]. Start with [first action].
Benefit-Focused Description Patterns
- "Make any machine ready for..."
- "Turn high-volume X into repeatable Y..."
- "Package X once. Install it anywhere."
- "Convert messy Y into reusable Z."
- "Create a repeatable operating system for..."
- "Automate the boring path from X to Y."
Authority Enrichment
When truthful, add credible origin context:
Weak:
A setup script for my machine.
Better:
A workstation setup system adapted from senior engineering practices and customized for agentic AI workflows.
Rules:
- Do not imply official endorsement.
- Use "adapted from," "inspired by," "based on public guidance," or "learned from" when accurate.
- Keep the reader benefit first.
Avoid
- "This is my project."
- "A portfolio project that..."
- "Just a small tool..."
- "Experimental repo..."
- Negative positioning like "not a toy project."
Checklist
- Does the reader know what they can use it for?
- Is the first action obvious?
- Does the description emphasize benefit over implementation?
- Is authority added without false endorsement?
- Is the one-liner short enough for a GitHub About field?