208건 · 관련도순
Creates workforce reports from uploaded, pasted, or connected HR data. Analyzes headcount, turnover, diversity, and organizational health, then presents key metrics, trends, methodology, caveats, and practical recommendations for leadership and HR teams.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan team structure and hiring by defining needed roles, headcount, timing, and costs. Produce text-based org charts and prioritized hiring roadmaps, and identify structural risks such as excessive management overhead or dependence on one person.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Size support and operations teams using demand ranges and queueing calculations, which estimate how work waits for service. Assess workload imbalance and service target risks, then build a quarterly hiring plan that accounts for training time and attrition.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Headcount and delivery-capacity planning — effective capacity from raw headcount, hire/contract/defer scenarios, and capacity-vs-commitment gap reports. Use when planning a quarter, sizing a hiring ask, or testing whether a roadmap fits.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plans the shape and size of the workforce — demand for roles, build-versus-buy, attrition, and sequencing hiring against budget. Use this to build a hiring plan, decide which roles to open and in what order, model attrition and backfill, plan for a growth or contraction scenario, or connect headcount plans to the budget.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Designs how an organization is structured — reporting lines, team boundaries, spans and layers, role definition, and workforce planning against the strategy. Use this to structure a new team, restructure an existing one, resolve unclear ownership between teams, plan headcount, or diagnose why a team underperforms for structural rather than individual reasons.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produces a copy-ready clause about a company adding people to one specific department in the last 6 months, plus the department-level headcount counts that drive the segment gate. Triggers on "they're hiring", "hiring surge", "growing their sales team", "scaling the team", "headcount growth", "who added SDRs", "companies that just built a marketing team". Outputs hiring_surge_line, a lowercase second-person clause that completes "Noticed <line>."
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enrich and research the people and companies the user names or supplies with Firecrawl Alexandria data: background on a person, a professional profile URL to look up, whether someone still holds a role, missing columns in a table or CSV of people or companies, firmographics for company domains (industry, headcount, funding, location), and pre-call or meeting briefs. Use whenever the request is about specific named people or companies, even without the word enrich, since roles, headcount and funding change faster than training data. Not for finding new prospects (use firecrawl-lead-gen) or a company's published press, sales or support contacts (use firecrawl-business-contacts).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prospects companies across developer-focused tech verticals for developer marketing agency outreach. Use this skill whenever a user provides a vertical (e.g. AI Agentic, IAC, DevTools, Observability, DevOps, FinOps, AI/SDLC, AI Orchestration, or any other tech vertical) and wants a list of prospect companies to target. Also trigger when the user says "prospect for", "find companies in", "give me leads for", "build a prospect list", or provides a vertical name alongside funding stage and headcount filters. Always use this skill — never attempt prospecting without following this structured workflow. The skill finds exact-fit companies only (never adjacent), maps a real outreach signal and email pain point for each, sources every data point with a URL, and outputs a unified nine-column table: Company, URL, LinkedIn, Headcount, Signal, Signal Sources, Geography, Pain Point, Pain Point Sources.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enrich and research the people and companies the user names or supplies with Firecrawl Alexandria data: background on a person, a professional profile URL to look up, whether someone still holds a role, missing columns in a table or CSV of people or companies, firmographics for company domains (industry, headcount, funding, location), and pre-call or meeting briefs. Use whenever the request is about specific named people or companies, even without the word enrich, since roles, headcount and funding change faster than training data. Not for finding new prospects (use firecrawl-lead-gen) or a company's published press, sales or support contacts (use firecrawl-business-contacts).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design or review annual operating budget — headcount plan, departmental spending, revenue targets, and variance tracking. Use when asked to "build our budget", "plan headcount for next year", or "review our spending".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design or review org structure - spans of control, reporting lines, role clarity, headcount plan, and team topology. Use when asked to "design our org", "should we restructure", "what is the right team structure", or "plan headcount for next year".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create, edit, and inspect spreadsheets for reusable budgets, models, and trackers. Check formulas and dependent totals, preserve unrelated data, and deliver an editable workbook or a link to the updated native spreadsheet.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan startup hiring from pre-seed through Series A. Organize roles, reporting lines, salaries, and equity compensation, then estimate staffing costs and hiring timelines around revenue goals, funding milestones, and budget limits.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review customer retention and customer success plans through six focused questions. Examine churn causes, customer segments, staffing capacity, hiring, and compensation, then produce a decision report with a verdict and three concrete next steps.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan hiring around business needs, estimate staffing costs, and develop salary bands, equity frameworks, and organizational structures. Use people metrics to examine retention and performance, producing practical proposals for growing companies and their HR leaders.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Makes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure. Use this to instrument a service, fix alerting that is ignored, set error budgets or reliability targets, prepare for on-call, or run a blameless post-incident review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting for review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-development practices around it. Use this to review an architecture or pull request for security, set secure coding standards, choose or tune SAST and DAST tooling, assess a third-party integration, or decide whether a design is safe to build.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Owns architecture, engineering delivery, infrastructure, data platform, and internal systems. Use this for build-versus-buy calls, technology selection, architectural direction, engineering capacity and delivery risk, technical debt tradeoffs, platform and tooling decisions, or when a technical choice has business consequences that need stating in business terms. Also use to judge whether a technical plan is sound before it is committed to.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Use this before saying something is done, fixed, or passing; before committing or opening a pull request; and whenever a claim of success has not been backed by command output.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Runs environment, health and safety on an operating site — hazard controls in order of effectiveness, incident recording and reporting obligations, and safety measurement that does not reward silence. Use this to build or audit a safety program, decide what controls a hazard actually needs, work out whether an injury is recordable or reportable, investigate an incident, or fix safety metrics that have stopped producing reports.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Designs AI systems, automations, and agent workflows for a business — identifying which manual work is worth automating, how to structure the system, which tools fit, and what could go wrong. Use this to automate part of an operation, design an agent or MCP workflow, reduce repetitive manual work, connect tools into a system, decide which automation to build first, or audit an automation that is not delivering.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Finds the root cause of a bug, test failure, or unexpected behavior before proposing any fix. Use this whenever something is broken and the cause is not yet proven — a failing test, a production error, intermittent behavior, or a symptom that appeared after a change. Also use when a fix has been attempted and did not work, or when the same bug keeps coming back.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.