low-altitude-interviewer
Skill0 starsChanged 7 months agoMITView on GitHub
Screen resumes and prepare interviews for low-altitude aviation roles such as drone inspection, facade cleaning, and related operational backends. Use this skill when the user wants candidate fit analysis, ranking, interview questions, or hiring recommendations shaped by low-altitude business needs rather than generic software hiring.
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when hiring or interviewing for low-altitude roles, especially backend positions that support drones, inspection, cleaning …
- Distinctive: line 29
treat device communication, realtime status return, task scheduling, media/file pipelines, work orders, and industrial system experience as …
- Distinctive: line 30
call out when a candidate is mainly frontend, mainly AI research, or mainly generic ecommerce backend
- Distinctive: line 31
when evidence is weak because the resume text is incomplete or OCR quality is poor, say so explicitly
- Distinctive: line 32
default reports, summaries, and screening tables to Chinese unless the user requests another language
- Distinctive: line 37
Read resumes with emphasis on internship and work responsibilities.
- Very specific: line 38
Use references/screening-rubric.md to score relevance.
- Very specific: line 41
Use references/output-templates.md when the user needs reusable screening tables, per-candidate summaries, or interview prep packs.
- Distinctive: line 42
If useful, produce a structured table the user can reuse in hiring review.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
Low-Altitude Interviewer
Use this skill when hiring or interviewing for low-altitude roles, especially backend positions that support drones, inspection, cleaning operations, device connectivity, mission execution, media handling, and work-order systems.
Read First
- the job description or the user's hiring intent
- the candidate resumes or candidate summaries
references/screening-rubric.mdreferences/output-templates.mdwhen you need reusable screening tables, candidate summaries, or interview question structure- any user-specific hiring preferences such as preferred stack, internship duration, location, or arrival time
Goals
- rank candidates against the actual low-altitude role rather than generic Java backend standards
- distinguish resume buzzwords from real internship responsibilities
- surface the most transferable experience for drone, inspection, and operational backend work
- generate interview questions that validate the candidate's claimed depth
Rules
- prioritize actual internship or work responsibilities over long technology keyword lists
- separate
strong fit,possible fit, andweak fitclearly - treat device communication, realtime status return, task scheduling, media/file pipelines, work orders, and industrial system experience as high-signal evidence
- call out when a candidate is mainly frontend, mainly AI research, or mainly generic ecommerce backend
- when evidence is weak because the resume text is incomplete or OCR quality is poor, say so explicitly
- default reports, summaries, and screening tables to Chinese unless the user requests another language
Process
- Extract the real hiring target: business context, stack, role seniority, and practical constraints.
- Read resumes with emphasis on internship and work responsibilities.
- Use
references/screening-rubric.mdto score relevance. - Group candidates into recommendation tiers.
- For shortlisted candidates, prepare targeted interview questions that test claimed responsibilities.
- Use
references/output-templates.mdwhen the user needs reusable screening tables, per-candidate summaries, or interview prep packs. - If useful, produce a structured table the user can reuse in hiring review.
Output
Provide:
- a short description of the hiring target
- candidate tiers such as
优先面,可面,不优先 - for each candidate: main responsibilities, matching points, risk points, and recommendation level
- suggested interview questions for the top candidates
- any evidence gaps caused by unreadable resumes, scanned PDFs, or missing experience details
In this repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- codex/AGENTS.mdAGENTS.md
- claude/CLAUDE.mdCLAUDE.md
- backend-refactorSkill
- buildSkill
- discussSkill
- docSkill
- frontend-designSkill
- frontend-refactorSkill
- pdfSkill
- repo-bootstrapSkill
- skill-maintenanceSkill
- tdd-executionSkill
- architecture-guardrailsSkill
- closed-loop-testingSkill
- harness-marathonSkill
- task-harnessSkill
- api-designSkill
- architecture-designSkill
- brainstormSkill
- codex-record-retrospectiveSkill
- database-designSkill
- integration-designSkill
- map-codebaseSkill
- migration-designSkill
- observability-designSkill
- planSkill
- query-optimizationSkill
- scalability-checkSkill
- service-boundary-reviewSkill
- api-change-checkSkill
- browseSkill
- bugfix-verificationSkill
- debugSkill
- incident-debugSkill
- performance-investigationSkill
- qaSkill
- reviewSkill
- security-reviewSkill
- verifySkill
- release-checkSkill
- shipSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

