القائمة
Fill out job application form fields with context-aware, tailored answers drawn from the candidate's CV and the job description
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/PramodDutta/qaskills --skill application-form-fillerيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
| name | Application Form Filler |
| description | Fill out job application form fields with context-aware, tailored answers drawn from the candidate's CV and the job description |
| version | 1.0.0 |
| author | thetestingacademy |
| license | MIT |
| tags | ["applications","career","job-search","automation"] |
| testingTypes | ["career"] |
| frameworks | [] |
| languages | ["markdown"] |
| domains | ["web"] |
| agents | ["claude-code","cursor","github-copilot","windsurf","codex","aider","continue","cline","zed","bolt"] |
Use this skill when the user wants to:
Application form answers should be direct and specific -> not a cover letter crammed into a text box. Each field has a purpose. Answer that purpose clearly, then stop.
The answer should feel like: A real person typed it, not a template was filled in.
Always read:
If the user hasn't provided a CV or JD, ask for them before writing.
Examples:
Format:
[Technology/skill] -> [X years]. [One sentence on what you used it for, with a
specific project or context]. [Optional: secondary tools in the same category].
Rules:
Examples:
Format:
[Specific thing about the company/role that's genuinely interesting -> not generic].
[How that connects to something the candidate has actually worked on].
[Optional: one line on why this domain, not just this company].
Rules:
Examples:
Format: List projects with one-line descriptions and links. Lead with the most relevant.
[Project Name] ([live URL] | [github URL]) -> [one line: what it is and one
proof point]. [Stack if relevant].
Rules:
Examples:
Format: For open-text fields:
[Primary skill] -> [X years]. [Specific use: what you built with it, in what context].
[Secondary skill] -> [X years]. [Same].
[Note any relevant gaps honestly].
For rating/dropdown fields: pick the honest level -> don't optimize for the highest rating if it's not accurate.
Rules:
Examples:
Format:
Current role + what you do there (1 sentence).
Relevant prior experience, briefly (1 sentence).
What you're looking for / why this role (1-2 sentences -> specific to the company).
Optional: one project or side work that's relevant (1 sentence).
Rules:
Examples:
Format: Condensed STAR (no labels, just flow)
[Context in one sentence]. [What you specifically did -> 2 sentences]. [Outcome
with a metric if possible -> 1 sentence].
Rules:
Examples:
Format: Answer with a genuine opinion. Pick one or two things and explain the reasoning briefly.
Rules:
Always wrap the answer in a plain code block so it's clean to copy-paste:
[Answer text here]
If providing multiple answers (one per field), use separate code blocks with a label above each:
Years of React experience:
4 years. Used it across Screenr (agentic hiring SaaS), a Tauri-based POS
system, and several client projects. Also used Next.js where SSR was needed.
Describe your backend experience:
...
| Field type | Target length |
|---|---|
| Single-line text | 1 sentence |
| Short answer | 2-4 sentences |
| Long answer / textarea | 100-250 words |
| "Describe your experience" | 150-300 words |
| "Tell us about yourself" | 100-200 words |
| Portfolio / links section | List format, no prose |
When in doubt, shorter is better. Recruiters skim form answers. The goal is to be clear and memorable, not comprehensive.
Repeating the JD: ❌ "I am interested in this role because you are looking for someone to build scalable backend systems..." ✅ "What caught my attention was the real-time constraint -> healthcare data at milliseconds latency is a different class of problem than most backend work."
Generic trait claims: ❌ "I am a fast learner who thrives in collaborative environments" ✅ [Just describe the actual work -> the traits come through]
Over-qualifying: ❌ "While I may not have exactly 5 years, I believe my experience..." ✅ "The role mentions 5 years -> I'm at 3, but the systems I've shipped are production-facing."
Listing without context: ❌ "React, Vue, Angular, Next.js, TypeScript, Node.js..." ✅ "React is my primary frontend framework -> 4 years across Screenr and several client projects. Vue and Angular for about 3 years each, mostly dashboards and admin tooling."
Padding to fill space: ❌ Adding projects or experience that aren't relevant just to look prolific ✅ Include only what's relevant to this specific role
Application portals ask QA candidates trap questions: years-of-experience per tool, salary expectations, and "have you worked with X" checkboxes. Keep a fact sheet with defensible numbers per tool (first project date to last use, not resume-padding totals) so every form gets identical answers; inconsistencies between your form, resume, and LinkedIn surface in background checks. For free-text "describe your testing experience" fields, paste a tight 3-sentence version of your summary, not the whole resume.
Adapted for QA professionals by The Testing Academy (thetestingacademy) from Resume Skills. The original work is used under the MIT License, reproduced in full below. Modifications to this file are released under the same license.
MIT License
Copyright (c) 2026 Resume Skills
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.