'improvement' 검색 결과

Turn interviews, surveys, and usage data into evidence-based user profiles, experience maps, and design recommendations. Plan usability tests, define success measures, and organize research findings to identify user problems and prioritize improvements.

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

• Create user personas from research data
• Map user actions, emotions, and pain points
• Plan usability tests for a proposed design

Create posts tailored to each social platform, build weekly or monthly content calendars, and turn existing articles or videos into new post ideas. The skill also guides opening lines, audience interaction, and improvements based on past performance.

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

• Drafting posts tailored to each social platform
• Planning a weekly or monthly content calendar
• Turning articles and videos into social posts

Routes content requests to specialist skills for writing, search visibility improvements, brand voice analysis, or planning. This deprecated skill identifies the intended task and points to the appropriate successor instead of producing content itself.

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

• Finding the right skill for writing a blog post
• Routing requests for topic planning and content calendars
• Finding tools for brand voice analysis and SEO improvements

Check Agent Skills for documentation structure and Python script behavior, then score quality and security posture. Get grades and improvement priorities, and use pass criteria in pre-commit checks or continuous integration, which runs checks automatically.

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

• Checking a newly authored skill before release
• Auditing existing skills and prioritizing improvements
• Testing bundled Python scripts and sample outputs

Build and review Kubernetes Operators, controllers that keep custom resources in their desired state. Included tools check resource definitions and Go reconciliation code, then assess operational capabilities and suggest improvements.

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

• Designing custom resource definitions for a new Operator
• Reviewing Go reconciliation code for common mistakes
• Assessing Operator capabilities and planning improvements

Turn company strategy into operational plans through process design, OKRs—objectives paired with measurable results—and regular reviews. Produce bottleneck analyses, efficiency scorecards, meeting schedules, and readiness reports for teams preparing to grow.

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

• Connecting company goals to department and team OKRs
• Finding process bottlenecks and planning improvements
• Assessing operational readiness for team growth

Map repeatable business processes by owner and analyze time spent working, waiting, or reworking. Using stage-level timing data, produce a process diagram, ranked bottlenecks, and cycle-time measures to focus improvements on the main constraint.

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

• Documenting procurement and employee onboarding workflows
• Identifying bottlenecks in slow business processes
• Making waits between teams visible

Review Python, JavaScript/TypeScript, and Go code for security issues using guidance for the project's languages and frameworks. Get prioritized findings, suggested improvements, or help writing new code with safer defaults.

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

• Review an existing application's security
• Create a report organized by severity
• Write new code with safer defaults

Analyze reviews, surveys, and other user feedback by user group. Summarize satisfaction scores, recurring complaints, positive themes, and the goals users want to achieve, then recommend product improvements based on frequency, severity, and business impact.

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

• Finding recurring themes across large volumes of user feedback
• Comparing satisfaction across user groups
• Prioritizing product improvements from customer complaints

Map the customer experience from discovering a product to recommending it. Create a table of interactions, actions, emotions, and pain points at each stage, then prioritize improvements to sign-up, initial use, and continued engagement.

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

• Mapping the full customer experience
• Finding friction during sign-up and initial use
• Identifying reasons customers leave

Run a structured sprint retrospective, a review of a short work cycle, using team feedback and delivery results. Identify shared themes and produce two or three prioritized improvements with owners, deadlines, and measures of success.

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

• Facilitating a team retrospective
• Grouping survey responses and team feedback
• Turning problems into assigned improvement actions

Turn development tickets, product requirements, or internal changelogs into release notes users can understand. Organize updates into features, improvements, and fixes, explain their benefits, and highlight changes that require users to take action.

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

• Creating release notes from development tickets
• Turning internal changelogs into user announcements
• Explaining updates that require user action

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

Improve a measurable target in a working system by tracing workload costs or scoring alternative implementations. Compare results against a baseline, keep confirmed improvements on a dedicated branch, and record experiments for review or resumption.

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

• Investigating the cost of a specific workload
• Comparing implementations against a measurable target
• Running improvement experiments within time and spending limits

Audit a website’s search visibility, content, and search demand to identify one to three priority improvements. Produce a concise, evidence-backed report focused on unpaid search visits from likely customers, with clear actions and limits.

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

• Choosing which SEO improvements to tackle first
• Finding search demand that existing pages do not address
• Comparing stronger and weaker pages on the same site

Access the equivalent of Claude Code's /pua:pro command from Codex CLI. The alias invokes the pro protocol for self-improvement, KPI performance measures, and configuration commands, with all processing kept local.

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

• Calling the equivalent of /pua:pro from Codex CLI
• Using the pro protocol for self-improvement and KPI commands
• Managing PUA settings locally

Organize SEO work into five stages, from keyword research and backlinks to page improvements, conversions, and local search. Apply a library of 41 prompts, selecting relevant guidance for the page and its current challenges.

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

• Research keywords and gaps in search results
• Plan backlinks and off-site authority
• Choose improvement prompts for a specific page

Improve writing, prompts, or skills through repeated review cycles that carry forward lessons and rejected approaches. Human feedback guides each pass by default, while saved history supports resuming work and tracking progress.

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

• Refining a prompt over several passes
• Improving a skill's output quality
• Making diagram instructions more consistent

Review code for security risks, logic bugs, and performance problems. Receive specific feedback explaining the affected lines or patterns, why they matter, and how to fix them, with required changes separated from optional improvements.

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

• Reviewing code changes before merging a pull request
• Checking input validation, access controls, and secret handling
• Finding inefficient queries and blocking operations

Check a paper’s numbers, comparisons, and evaluation scope against raw experiment files. A fresh reviewer receives only source evidence and paper files, then reports discrepancies in rounding, aggregation, settings, and reported improvements.

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

• Verify reported numbers before paper submission
• Check averages and counts across experiment runs
• Recalculate claimed percentage improvements

Turn a research report and experiment results into an English paper with figures, LaTeX source, and a compiled PDF. Coordinate planning, drafting, Gemini reviews, and two revision rounds, preserving PDFs and an improvement log.

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

• Turning a research report into a paper
• Drafting a paper from experiment results
• Preparing a paper for ICLR, NeurIPS, or ICML

Improve a compiled LaTeX paper through two rounds of Claude review, edits, and recompilation. The workflow addresses inconsistent reasoning, unsupported claims, unclear writing, and visual presentation, while keeping a cumulative log of changes.

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

• Polish a generated paper before submission
• Correct inconsistencies and unsupported claims
• Improve figures, tables, and page layout

Review Python, JavaScript/TypeScript, and Go code for security issues using guidance for the project's languages and frameworks. Get prioritized findings, suggested improvements, or help writing new code with safer defaults.

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

• Review an existing application's security
• Create a report organized by severity
• Write new code with safer defaults

Review and improve code changes on the current branch using Pipecat conventions. Refine names and structure, add type hints and documentation, check example patterns, and make conservative performance improvements while preserving compatibility.

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

• Cleaning up branch changes before review
• Adding missing type hints and documentation
• Checking Pipecat service and example patterns