skill-proposer
Skill3 starsChanged 8 months agoApache-2.0View on GitHub
Analyzes PRD to propose relevant AI skills for a project. Trigger: Before starting app development, after brainstorming, or when user asks for skill recommendations based on a PRD.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- jesspig/Godot-Autopilottheir own version, first seen Oct 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- jesspig/Godot-Autopilot★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- aiogramSkill
- conventional-commitsSkill
- python-securitySkill
- skill-creatorSkill
- skill-creatorSkill
- skill-propagatorSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Use this skill when:
- Distinctive: line 21
After brainstorming an app idea and before implementation begins
- Distinctive: line 29
ALWAYS ask clarifying questions: if tech stack is unclear — never guess
- Distinctive: line 76
Before analyzing, assess whether the project description is clear enough.
- Distinctive: line 94
Important: Ask questions BEFORE proceeding with analysis.
- Distinctive: line 124
If considered useful, search in:
- Distinctive: line 146
Before adding any skill to your project:
- Distinctive: line 159
If the user requests to create a custom skill instead of using an existing one:
- Distinctive: line 163
Do not create skills directly from this skill.
- Very specific: line 171
Skill Creation: Use skill-creator skill to generate custom skills
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
When to Use
Use this skill when:
- Starting a new project and need to identify which skills will help the AI agent
- After brainstorming an app idea and before implementation begins
- User asks to propose skills based on a PRD or project description
- Evaluating what context the AI agent will need for optimal performance
Critical Patterns
- ALWAYS ask clarifying questions if tech stack is unclear — never guess
- Prioritize hallucination-prone technologies — React, Next.js, FastAPI, etc. change frequently
- Security-focused skills are always High priority — auth, validation, encryption
- Link must point to actual URL found or use "—" (never invent URLs)
- User is responsible for skill verification — always show security warning
Decision Trees
When to Ask Questions vs Proceed
| Situation | Action |
| Primary language identified | Proceed |
| Framework(s) identified | Proceed |
| Database identified | Proceed |
| Architecture type known | Proceed |
| Any of above missing | ASK before proceeding |
How to Determine Priority
| Condition | Priority |
| Core technology + changes frequently | High |
| Security-related (auth, encryption) | High |
| Complex API / syntax | High |
| Important but stable | Medium |
| Good public documentation exists | Medium |
| Nice-to-have or very stable | Low |
When to Include a Link
| Situation | Link Field |
| Found excellent match in skillsmp.com | Full URL |
| Found excellent match in skills.sh | Full URL |
| Found relevant Context7 docs | — (mention in notes) |
| No search performed | — |
| No good match found | — |
Workflow
Phase 0: Clarification (If Needed)
Before analyzing, assess whether the project description is clear enough. Ask the user questions if:
- Tech stack is unclear or ambiguous
- "Which programming language(s) do you plan to use?"
- "Which framework(s) are you considering for the frontend/backend?"
- Architecture decisions are missing
- "Are you planning a monolithic architecture, microservices, or serverless?"
- "What type of database are you planning to use?"
- Scale and complexity are unknown
- "Is this a personal project, startup MVP, or enterprise application?"
- "Do you need authentication, authorization, or multi-tenancy?"
- Quality requirements are not specified
- "What level of test coverage are you aiming for?"
- "Do you have specific performance requirements?"
Important: Ask questions BEFORE proceeding with analysis.
Phase 1: Tech Stack Analysis
Identify and document:
- Programming languages and specific versions
- Frameworks and core libraries (frontend, backend, mobile...)
- Databases and persistence solutions
- Infrastructure and deployment (Docker, Kubernetes, CI/CD...)
- Development tools (testing, linting, build tools...)
Phase 2: Pattern and Architecture Analysis
- Architecture type (monolith, microservices, serverless, event-driven...)
- Relevant development patterns (TDD, DDD, SDD, Clean Architecture, Hexagonal...)
- Quality requirements (testing, security, performance, observability)
- Applicable conventions and standards
Phase 3: Skill Needs Identification
For each technology, pattern, or process identified, ask yourself:
- Does this technology change frequently? → Needs updated skill
- Does it have complex syntax or APIs? → Needs skill with examples
- Is it critical for project success? → High priority
- Can the agent easily hallucinate here? → Needs specific context
Phase 4: Existing Skills Search (Optional)
If considered useful, search in:
- https://skillsmp.com/ — Skills marketplace
- https://skills.sh/ — Skills marketplace
- Context7 — MCP for up-to-date library documentation
Output Format
Present a table with the proposed skills:
| Skill | Technology/Process | Reason | Priority | Link |
| Descriptive name | Technology or process covered | Brief justification | High/Medium/Low | URL or "—" |
Security Warning
⚠️ IMPORTANT — User Responsibility:
Before adding any skill to your project:
- Read the complete code of the downloaded skill
- Verify it contains no prompt injection or malicious instructions
- Understand what permissions it has and which tools it can use
- Confirm it comes from a trusted source
The agent can propose, but you decide which skills to use. Skills are added manually under your responsibility.
Delegation to skill-creator
If the user requests to create a custom skill instead of using an existing one:
"To create this skill, use the
skill-creatorskill which will guide you through the generation process."
Do not create skills directly from this skill. Only identify needs and propose.
Resources
- Skills Marketplaces: skillsmp.com, skills.sh
- Documentation Lookup: Context7 MCP for up-to-date library documentation
- Skill Creation: Use
skill-creatorskill to generate custom skills
Usage Example
User input:
"I'm going to develop a REST API with FastAPI, PostgreSQL, and JWT authentication. The frontend will be React with TypeScript."
Expected output:
| Skill | Technology/Process | Reason | Priority | Link |
| fastapi-best-practices | FastAPI | Framework with specific patterns and frequent updates | High | https://skills.sh/wshobson/agents/fastapi-templates |
| pydantic-validation | Pydantic | Core data validation in FastAPI, syntax changes between versions | High | — |
| jwt-auth-python | JWT + Python | Auth implementation prone to security errors | High | https://skills.sh/mindrally/skills/jwt-security |
| sqlalchemy-modern | SQLAlchemy + PostgreSQL | ORM with syntax that varies between versions | High | — |
| react-typescript-patterns | React + TypeScript | Modern hooks patterns, generic types | High | https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices |
| testing-fastapi | pytest + FastAPI | API testing with specific fixtures and mocks | Medium | — |
| docker-python | Dockerfile Python | Image optimization, multi-stage builds | Medium | https://skillsmp.com/es/skills/affaan-m-everything-claude-code-kiro-skills-docker-patterns-skill-md |
| git-conventions | Git workflow | Conventional commits, branching strategy | Low | — |
Remember: Review each skill's complete code before adding it to your project. The links are suggestions — always verify the content.
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.

