'closing' 검색 결과

Turn a talking-head or selfie recording into a vertical video about a Muse experience. Preserve the original narration while showing synchronized chat exchanges, actual work outputs, interface elements, and message sounds to create a shareable clip.

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

• Turning a Muse experience recording into a vertical clip
• Adding chat exchanges in sync with narration
• Showing actual pages and files alongside a creator's story

Organize open pull requests before a release, classify what to merge or defer, and track decisions in a resumable document. Guide review, merging, follow-up fixes, and closing requests already covered by other changes.

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

• Sort a backlog of pull requests before a release
• Prioritize bug fixes for the next version
• Resume interrupted reviews from a progress document

Review open commitments in acc and record success or failure with supporting notes. Distinguish self-assessment from owner validation or observed real-world results, and keep commitments open when they are still waiting on an outcome.

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

• Reviewing open commitments in acc
• Closing commitments with verified outcomes
• Distinguishing self-assessment from external validation

Set communication rules for teams of AI agents. The skill explains when to use direct messages or broadcasts, how leads review plans, how teammates shut down safely, and how to troubleshoot stalled handoffs or missing communication tools.

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

• Establishing communication rules for a new agent team
• Choosing direct messages or team-wide broadcasts
• Reviewing and approving a teammate's work plan

Design hands-on workshops with short explanations, immediate exercises, and quick self-checks. Use brief dialogue between a teacher and an assistant to guide practice, then finish with a small project that combines what learners have tried.

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

• Create a workshop built around hands-on practice
• Turn long explanations into short briefs and exercises
• Write guiding dialogue for a teacher and assistant

Track multiple M&A, financing, or restructuring deals in an Excel workbook. Organize stages, milestones, deadlines, and assigned tasks, flag delays and risks, and prepare a weekly review covering developments and upcoming work.

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

• Reviewing progress across multiple active deals
• Tracking bid deadlines and expected closing dates
• Managing assigned tasks and overdue items across deals

Turn ideas, notes, or technical material into LinkedIn posts ready to copy and paste. Organize hooks, short sections, closing prompts, and hashtags, using Unicode characters to give plain text the appearance of bold or italic styling.

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

• Turn technical material into a LinkedIn post
• Format an existing draft for easy scanning
• Share a lesson drawn from work experience

Keep a short, persistent work journal so an agent can resume across sessions. Record completed work, current status, next steps, and unsuccessful attempts, then read the latest entry when restarting or summarize the work when closing it.

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

• Recording progress at the end of a session
• Resuming work from the latest journal entry
• Saving key decisions and unsuccessful attempts

Generate trading signals using Smart Money Concepts, a framework for interpreting institutional trading behavior. Analyze trend continuation, reversals, price gaps, and order concentration zones, then combine structural signals and gaps to determine a trading direction.

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

• Build signals from trend continuation and reversal patterns
• Filter structural signals using price gaps
• Adjust swing detection and closing-price break rules

Connect Gmail, Calendar, and Contacts to track people awaiting replies and promises still outstanding. Get a prioritized digest with supporting quotes, email links, deadlines when available, and background context to help prepare a response.

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

• Set up Google account connections
• Check who is waiting for a reply or promised action
• Review someone’s history before preparing a response

Check YAML frontmatter, the metadata at the top of knowledge pages, for formatting and identity errors. Explain why gbrain holds files during sync, preview proposed changes, and repair supported problems after approval.

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

• Audit metadata across knowledge pages
• Investigate files held during sync
• Preview and repair formatting errors

Review a sales opportunity using deal records, emails, and meeting notes. Get an evidence-based assessment of closing likelihood, missing information, risks, and prioritized next steps, with a comparison against the stage recorded in your sales system.

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

• Assess whether a deal is likely to close
• Check whether the recorded sales stage matches the evidence
• Identify missing information before a sales review

Close out a sales day by reconciling meetings with call records, identifying CRM updates, and collecting commitments from both sides. Receive a day-end wrap with call statuses and the three highest-priority actions for tomorrow.

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

• Checking for unprocessed calls at the end of the day
• Identifying CRM updates after meetings
• Collecting commitments and deadlines from both sides

Prepare income statements with prior-period and budget comparisons, highlight significant differences, and explain their drivers. Reference formats for balance sheets and cash flow statements also support financial reporting and period-end adjustments.

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

• Preparing monthly or quarterly income statements
• Investigating significant differences from budget
• Summarizing financial results for leadership

Update the GitHub issue linked to completed Factory work after verifying the target repository. Remove specified triage labels and, for open issues, add a pending-close label and completion comment without closing the issue.

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

• Updating an issue after Factory work is complete
• Removing triage labels from completed work
• Adding a pending-close label and completion comment

Set up Herdr Kit and its Mastra Code integration, manage repository synchronization, and create or remove managed worktrees, separate working copies for review or development. The workflow checks supported operations and verifies the resulting manager state.

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

• Installing Herdr Kit and the Mastra Code integration
• Keeping repositories synchronized after closing their workspaces
• Creating or removing managed Review and Work worktrees

Work through difficult business decisions such as layoffs, product closures, or changes in company direction. Compare immediate and long-term consequences, map who is affected, and prepare a clear explanation and communication plan.

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

• Weighing layoffs and their impact on the team
• Comparing options for closing a product line
• Considering a co-founder's role change or departure

Manage shared project tasks in Beads, from finding available work and claiming tasks to tracking dependencies, recording follow-up work, and closing completed items. Keep project status available across sessions and handoffs.

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

• Find tasks that are ready to start
• Claim tasks and record completion
• Track blockers and dependencies

Review a completed development task against its acceptance criteria, check differences from design and architecture documents, and prompt code review. After approval, update the task's status and identify the next story to work on.

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

• Checking acceptance criteria before closing a development task
• Recording differences between implementation and design
• Remembering code review before marking work complete

Turn game bug descriptions or suspected code problems into structured reports with reproduction steps, severity, and priority. Follow reported bugs through fix verification and closure, recording test results or manual checks before marking an issue closed.

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

• Turning a bug description into a structured report
• Finding potential bugs in a specific file
• Verifying a fix through tests or manual checks

Review game code for architecture, coding standards, testability, and performance concerns. Get findings tied to specific code, checks against recorded design decisions, and a report separating required fixes from optional improvements.

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

• Reviewing game code before closing a development task
• Checking implementation against recorded architecture decisions
• Finding testability gaps and performance concerns

Organize Happy's GitHub issues, find duplicates, and check whether reported bugs are fixed on main, the primary development branch. Prepare replies and proposed actions for maintainer review, with explicit approval required before changes affecting contributors.

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

• Grouping open issues and identifying duplicates
• Checking whether reported bugs are fixed on main
• Drafting replies and issue closure comments

Recheck older NemoClaw bug reports against the reported and newest releases, then prepare evidence-backed recommendations for maintainers. It documents reproduction results and proposed updates for approval without automatically closing issues.

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

• Rechecking older bug reports
• Comparing reported and newest releases
• Preparing evidence-backed issue updates

Evaluate whether Google SecOps rules detect threats described in articles or supplied text. Generate simulated attack logs, identify coverage gaps, summarize matching rules, and create rules for uncovered threats, with user approval before adding them.

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

• Evaluate detection coverage for threats described in a blog
• Test existing rules with simulated attack logs
• Review matching rules and their alerting status