Results for “need”

Assess whether source code is ready to deploy to Azure — the check BEFORE infrastructure work. Evaluates build health, app completeness, dependencies and local services, stack compatibility, and deployment feasibility. Answers questions about what your app needs before it can be deployed — frameworks, dependencies, and configuration. Checks whether dependencies are compatible and identifies deployment blockers and unsupported frameworks. WHEN: "evaluate my repo", "is my app ready to deploy", "what does my app need to deploy", "what do I need before deploying", "does my app need", "can I ship this to Azure", "scan my repo for issues", "is this app deployable", "check if my app is ready for Azure", "do I need a Dockerfile", "what's blocking my deployment", "are there any blockers", "are my dependencies compatible", "does Azure support my framework", "what needs to change before deploying", "check my app configuration".

The English summary is being prepared. Showing the original description.

Assess whether source code is ready to deploy to Azure — the check BEFORE infrastructure work. Evaluates build health, app completeness, dependencies and local services, stack compatibility, and deployment feasibility. Answers questions about what your app needs before it can be deployed — frameworks, dependencies, and configuration. Checks whether dependencies are compatible and identifies deployment blockers and unsupported frameworks. WHEN: "evaluate my repo", "is my app ready to deploy", "what does my app need to deploy", "what do I need before deploying", "does my app need", "can I ship this to Azure", "scan my repo for issues", "is this app deployable", "check if my app is ready for Azure", "do I need a Dockerfile", "what's blocking my deployment", "are there any blockers", "are my dependencies compatible", "does Azure support my framework", "what needs to change before deploying", "check my app configuration".

The English summary is being prepared. Showing the original description.

Synthesises training survey responses and manager notes into a DRAFT training needs report by role: coded needs with record counts per role (n of N), the evidence type behind each count, anonymised quotes cited to record codes, disagreements between what staff report and what managers observe, gaps where a role is under-represented or a required skill has no evidence, and follow-up questions to settle before any course is designed. Never rates an individual, ranks a team or turns a count into a competence verdict. Use when the user asks to "analyse this training survey", "what training do our teams need", "summarise the manager feedback on skills gaps", "build a training needs analysis by role" or "which roles have the biggest skill gaps". Do not use for turning an agreed need into a course, use course-outline-builder instead; for exit interviews, use exit-interview-synthesis. Drafts for human review; never approves, authorises or signs off.

The English summary is being prepared. Showing the original description.

Generate cinematic clips with Seedance 2.0 using camera directions, multiple shots, and synchronized speech, sound effects, and ambience. Reference images help maintain character appearance, while the skill guides prompt structure, provider selection, previews, and checks of the finished clips.

• Producing trailers and teaser clips
• Generating multiple shots with a consistent character
• Creating dialogue scenes with matching mouth movements

Review unread customer email threads, sort them by the response needed, and prioritize urgent deals. Prepare concise replies in the sender's usual style, while highlighting sensitive messages and questions that need the user's input.

• Find customer emails that need a reply
• Prioritize replies by deal timing and urgency
• Draft scheduling replies using calendar availability

Evaluate substantial software changes against the actual problem, current system, and concrete users or components that need them. Choose a sufficient scope, assess consequences, and, when implementation is requested, make the change and verify its behavior.

• Assessing whether a feature proposal is needed
• Reducing the scope of a refactor or migration
• Checking who needs a proposed API or data field

Set up an ElevenLabs API key for MCP tools that connect agents to ElevenLabs. Checks existing credentials, guides key creation when needed, validates access, and saves a working key in a .env file.

• Setting up ElevenLabs MCP tools for the first time
• Resolving errors caused by a missing API key
• Checking whether an existing API key works

Find, generate, and prepare media for HyperFrames projects, saving assets locally with records for reuse. Covers images, music, voiceovers, transcription, captions, background removal, media edits, and visual treatments such as color correction or retro styling.

• Find and save images, music, and sound effects
• Produce voiceovers, transcripts, and captions
• Correct dark footage or apply retro styling

Review open GitHub issues for herdr and organize them into a concise Markdown table. Each row shows urgency, a recommended action, issue age, reactions, and a short reason to help decide what needs attention.

• Deciding which open issues need immediate fixes
• Preparing a queue of feature requests and quality improvements
• Reviewing older issues and reports that need more evidence

Decide whether a task can be completed with available access or needs another person's accounts, files, or stored memory. When a handoff is necessary, send that person one direct message with the full request and its source thread.

• Request work that needs another person's account access
• Ask for work involving another person's files or stored memory
• Send a complete request linked to its source thread

Sort a Superhuman inbox into messages needing a reply, waiting for others, useful information, and noise. Receive a clear attention list, then apply requested actions such as archiving, labeling, reminders, or unsubscribing.

• Finding messages that need a reply
• Reviewing requests awaiting a response
• Sorting newsletters and notifications

Triage proposed personal data uses to determine whether they can proceed, need a privacy impact assessment, require a legally mandated assessment, or must stop. Results explain policy conflicts, applicable triggers, and conditions to address before proceeding.

• Checking whether a new feature needs a privacy assessment
• Reviewing proposed data uses involving a vendor
• Finding conflicts with privacy policy commitments

Triage quick legal questions against company risk guidelines and return a brief proceed, review, or hold response. It checks for hidden issues in apparently simple requests and identifies the next step when further review is needed.

• Answering a product manager's quick legal question
• Checking permission to display customer logos
• Spotting data and consent issues in feature changes

Review marketing copy for factual statements, comparisons, implied promises, and absolute claims that need evidence or revision. Receive a claim-by-claim assessment, suggested wording, and a list of supporting data needed before publication, informed by applicable advertising standards.

• Check landing page claims and supporting evidence
• Review competitor comparisons in ads
• Revise absolute or potentially misleading wording

Review open employee leave cases for legal deadlines and required decisions. Identify cases needing action around leave designation, certification, or entitlement exhaustion, explain why they need attention, and summarize cases without issues briefly.

• Reviewing leave cases each week
• Finding upcoming designation or certification deadlines
• Checking cases nearing the end of leave entitlement

Document frontend data needs for backend developers. Use when frontend needs to communicate API requirements to backend, or user says 'backend requirements', 'what data do I need', 'API requirements', or is describing data needs for a UI.

The English summary is being prepared. Showing the original description.

Generate cohesive, project-specific SVG icon sets for websites and applications. Use this skill whenever the user needs custom icons, an icon set for a website or app, icons for a client project, or mentions needing SVG icons that look consistent together. Also trigger when the user describes a project and icons would naturally be part of the deliverable — e.g. 'I'm building a site for a plumber' implies they'll need service icons. Trigger on: 'icons for', 'icon set', 'custom icons', 'SVG icons', 'make me icons', 'I need icons', 'website icons', 'project icons', or any request for consistent visual assets for a web project. Produces individual SVG files with a consistent style engine, not generic icon library lookups.

The English summary is being prepared. Showing the original description.

Elite incident response and legal compliance guidance for data breaches under GDPR Articles 33 & 34. Use when: (1) User reports a data breach or security incident — including "is this even a personal data breach?" triage, (2) User asks about breach notification obligations or deadlines, (3) User mentions "72 hours", Art. 33, Art. 34, or notification requirements, (4) Discussion involves security incidents affecting personal data, (5) User needs breach risk assessment using ENISA methodology, (6) User mentions "Data Breach" or "Incident" or "Data Leakage" or "Ransomware" or "Exfiltration", (7) User needs to determine Controller vs Processor obligations, (8) Cross-border breach scenarios requiring Lead SA determination, (9) User needs a mitigation playbook or immediate response recommendations, (10) User needs audit-ready breach documentation (.docx) or an EDPB-template-aligned breach notification / evidence file — including follow-up and withdrawal notifications, (11) Breach involves an AI system requiring AI Act Art. 73 serious incident screening.

The English summary is being prepared. Showing the original description.

This skill should be used when the user asks to determine what tax filings they need, wants to know if they must file a tax return (確定申告), asks about consumption tax obligations (消費税), or needs help understanding their filing requirements. Trigger phrases include: "確定申告が必要か", "申告の種類", "消費税の届出", "課税事業者かどうか", "何を申告すればいい", "申告要否", "税金の申告", "住民税の申告".

The English summary is being prepared. Showing the original description.

Recommend relevant Isabelle/HOL or Coq standard library theories, lemmas, and tactics based on proof goals. Use when: (1) Users need library lemmas for their proof, (2) Proof goals match standard library patterns, (3) Users ask what libraries to import, (4) Specific lemmas are needed for list/set/arithmetic operations, (5) Users are stuck and need to know what library support exists, or (6) Guidance on find_theorems/Search commands is needed. Supports both Isabelle/HOL and Coq standard libraries.

The English summary is being prepared. Showing the original description.

Debug proof failures using counterexamples from Nitpick (Isabelle) or QuickChick (Coq) to identify specification errors, missing preconditions, and proof strategy issues. Use when: (1) A proof attempt fails and you need to understand why, (2) Counterexamples are generated by Nitpick or QuickChick, (3) Specifications may be incorrect or incomplete, (4) Theorems need validation before proving, (5) Missing preconditions or lemmas need identification, or (6) Proof failures need explanation and correction suggestions. Supports both Isabelle/HOL and Coq equally.

The English summary is being prepared. Showing the original description.

Conduct insurance needs analysis with gap identification. TRIGGERS - Use when user needs help with insurance-needs-analysis related tasks.

The English summary is being prepared. Showing the original description.

Map the needs of the people you're building or exploring for, independently of solutions, using Allen's User Needs Mapping methodology. Identifies underserved needs that feed into the Opportunity Solution Tree.

The English summary is being prepared. Showing the original description.

"Apply Self-Determination Theory to analyze motivation quality along the autonomy continuum and design interventions that satisfy basic psychological needs. Use this skill when the user needs to diagnose why intrinsic motivation is declining, evaluate incentive structures for motivational crowding, design need-supportive environments, or when they ask 'why did rewards backfire', 'how to foster intrinsic motivation', or 'what needs drive engagement'.".

The English summary is being prepared. Showing the original description.