interview-readme
Skill4 starsChanged 2 months agoNo licenceView on GitHub
Rewrite a project's README.md so it doubles as an interview walkthrough guide the author can read and confidently explain the project from. Use when the user asks to "make the README interview-ready", "rewrite the README as an interview guide", "help me explain this project in an interview", "write a README I can walk an interviewer through", "prepare this project for interviews", or invokes /interview-readme. Also trigger when the user has an interview coming up and wants to answer "Can you walk me through this project?" for a repo they built. The rewritten README explains, in simple English, what the project does, the problem it solves, the overall architecture, the technologies used and why they were chosen, how the main features work, the request/response flow, key technical decisions and trade-offs, challenges faced and how they were solved, and possible future improvements. Not for adding badges, topic tags, or GitHub discoverability work — use github-repo-seo for that.
- Reads credentials
In this repository25 other files it gives its agents.
- code-qualitySkill
- design-to-codeSkill
- dockerSkill
- FastAPI Development (Hybrid)Skill
- fastapiSkill
- FastMCP DevelopmentSkill
- frontend-designSkill
- github-repo-seoSkill
- Knowledge RouterSkill
- kubernetesSkill
- n8n-code-javascriptSkill
- n8n-code-pythonSkill
- n8n-expression-syntaxSkill
- n8n-mcp-tools-expertSkill
- n8n-node-configurationSkill
- n8n-validation-expertSkill
- n8n-workflow-patternsSkill
- nextjs-app-routerSkill
- OpenAI Agents SDK DevelopmentSkill
- postgres-neonSkill
- pythonSkill
- skill-creatorSkill
- spring-bootSkill
- ui-ux-engineeringSkill
- oss-contributeSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. About 0 are common, 19 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈19
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.