'deliverable' 검색 결과

Write and review launch prompts for agents working autonomously for hours or days. Define successful deliverables, excluded partial results, stopping rules, worker handoffs, and evidence-based review requirements so completion can be assessed against explicit criteria.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning vague requests into precise task briefs
• Defining stopping rules for long autonomous runs
• Specifying deliverables for parallel workers

Create and edit spreadsheet files, clean messy tables, and convert tabular formats. Add formulas, formatting, and charts while following existing template styles, then recalculate formulas and check for errors before delivering the spreadsheet.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clean messy CSV data into a spreadsheet
• Add formulas and charts to an Excel workbook
• Update a workbook using its existing formatting

Turn existing GEO audits, which assess readiness for AI search citations, into one client report. Combine scores, technical and content findings, platform comparisons, and a prioritized action plan written for business owners and marketing leaders.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Combining multiple GEO audits into a client report
• Explaining AI search readiness to business leaders
• Prioritizing improvements by impact and effort

Check deliverables before marking a task complete. Review the requested file format, confirm every reference file was used, and compare the result with the original request to catch omissions and work that misses the goal.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking deliverables before submission
• Reviewing coverage of multiple reference files
• Verifying requested output formats

Find generated files that are missing from their expected locations in isolated or temporary execution environments. Search confirmed directories, identify the right file, copy it to the intended destination, and verify that it is readable and nonempty.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find files after a tool reports successful generation
• Recover deliverables saved in temporary directories
• Correct files saved in unexpected nested folders

Produce a master track and separate audio parts through a structured Python workflow. Apply filters and reverb, export WAV files with consistent settings, package them in a ZIP archive, and check that the deliverables meet the requested specifications.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Export a master track with separate audio parts
• Apply filters and reverb to audio
• Check duration and format across deliverables

Split large feature requests or user stories, descriptions of what users need, into smaller deliverable pieces. Eight patterns guide the breakdown, with acceptance criteria and checks that each piece provides value and can be developed and tested independently.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Breaking down work that will not fit in one sprint
• Clarifying backlog items that are too large to estimate
• Separating stories with multiple acceptance scenarios

Plan work across several AI agents by defining task owners, deliverables, dependencies, and acceptance criteria. Choose a finite workflow or repeated improvement cycles, then review results before allowing dependent tasks to proceed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Divide a project among several AI agents
• Choose between a planned workflow and repeated improvement
• Define acceptance criteria for each deliverable

Turn ready project tasks into clear instructions for AI workers, with defined ownership, deliverables, acceptance criteria, and reporting rules. Handle assignment notifications and check submitted results before passing them to the project management workflow for acceptance.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing instructions for ready project tasks
• Defining deliverables and acceptance criteria
• Checking submitted worker results

Choose a suitable deliverable format for a research request, such as a report, table, memo, or timeline. Preserve any format the user specifies and return a short format label for the current request.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing a deliverable format for a research request
• Selecting a format based on how readers will use the findings
• Passing a user's chosen format to the next research step

Prepare scientific figures for papers, reports, and saved deliverables by checking data fidelity, chart choice, labels, axes, and color consistency. Verify exported figures for overlapping text and readability while keeping fonts, palettes, and framing configurable.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing scientific figures for a paper or report
• Checking excluded data and summary statistics
• Improving labels, axes, and color consistency

Turn enterprise red-team findings into client-facing reports with clear observations, business impact, remediation, and reproducible evidence. The skill provides report structure, severity and status guidance, and a Markdown-to-DOCX workflow with embedded screenshots and delivery checks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing final enterprise red-team reports
• Explaining findings to technical and business readers
• Packaging screenshots and evidence into DOCX

Create and edit spreadsheet files, clean messy tables, and convert tabular formats. Add formulas, formatting, and charts while following existing template styles, then recalculate formulas and check for errors before delivering the spreadsheet.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clean messy CSV data into a spreadsheet
• Add formulas and charts to an Excel workbook
• Update a workbook using its existing formatting

Organize complex tasks using persistent Markdown files for plans, research notes, and final deliverables. Track completed phases, decisions, and errors, and revisit the plan before major actions to keep work aligned with its goal.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning a task with multiple stages
• Organizing research findings and sources
• Recording progress, decisions, and errors

Create or redesign self-contained single-file HTML artifacts with a visual direction shaped by the user's brief, project, and subject. Use when HTML is the deliverable for a report, explainer, landing page, presentation, tool, mixed artifact, or broad request. This is the collection's only implicit router. Route clear wireframe, prototype, mockup, plan, or diagram requests to the matching direct-invocation specialist when available. Do not use for ordinary application implementation when a standalone HTML file is not the deliverable.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

FAIR-aligned exposure quantification: turns a pile of recon findings into a defensible 0-100 + A-F org risk score (Likelihood x Impact, three ownership-aware factors: exposure/threat/impact), an ownership + proof demotion cap so unproven or weakly-owned findings can't inflate the number, a $-denominated FAIR loss-magnitude estimate (IBM/Ponemon per-record cost bands, cross-source record dedup, threat-factor annualization), attack-path amplification (curated red-team chain catalog + generic graph-walk engine, with a kill-chain vs shared-fate honesty gate), and a board-ready one-pager deliverable (hero $ + letter grade + top-3 findings + top attack path + the ask). Extends osint-methodology's severity rubric and client deliverable templates with quantification. Passive analysis only -- operates on findings already collected, no target traffic, no API keys. Use when asked to score risk, quantify exposure, estimate breach cost, build a board report, translate technical findings to dollars, or explain why a grade or dollar figure came out the way it did.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Comprehensive OSINT methodology for external red-team operations and authorized attack-surface assessments. Covers the 6-stage recon pipeline (seed → asset expansion → enrichment → exposure analysis → convergence → operator-armed active validation) with connector-resilience and stage-vs-gating discipline, asset-graph discipline, severity rubric, confidence upgrade workflows, time budgeting, identity-fabric mapping, breach×identity correlation with per-person identity dossiers, detectability tagging, detection-aware probing, WAF/CDN bypass, vulnerability prioritization, phishing infrastructure planning, bug bounty submission, and client deliverable templates. Use when planning or executing reconnaissance against authorized targets, mapping an organization's external attack surface, investigating a person/entity, or producing client deliverables.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when producing a polished, Commonly-branded deliverable (.docx brief / memo, .xlsx data matrix, .pptx deck) and you do not have specific brand guidance from the user. Trigger on: 'write me a brief', 'one-pager', 'memo', 'data sheet', 'status matrix', 'short deck', 'summary deck', 'closing slide', 'final deliverable'. Routes to `officecli merge` with one of three pre-built starter templates that already carry the Commonly palette, fonts, and structure — so you populate content with one merge call instead of 30 individual `officecli set` commands. DO NOT use for fundraising decks (use `officecli-pitch-deck`), academic papers (use `officecli-academic-paper`), or financial models (use `officecli-financial-model`).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate a deliverable markdown report by merging all /money-save snapshots for a project. Produces a shareable, dated document at ~/.smtm/reports/{project}/. Useful for sharing progress with co-founders, advisors, investors, or for personal review weeks/months later. Use when the user wants to package up accumulated state into a readable artifact. Triggered by: 'package this up', 'make me a report', 'export for partner', 'give me the deliverable', '出报告', '打包', '整理一份', '给合伙人看的'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Score an existing reader-facing deliverable and emit a deterministic PASS/FAIL scorecard plus bounded repair plan; use after synthesis, not to rewrite content.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.