'first week' 검색 결과

신입 직원의 온보딩 계획을 한 페이지 HTML로 정리합니다. 첫날과 첫 주 일정, 상사와 동료 안내, 30·60·90일 목표, 참고 자료와 완료 조건을 모읍니다.

• 신입 직원의 첫 주 일정 준비
• 30·60·90일 목표 설정
• 상사·온보딩 동료·참고 자료 공유

Create a role-specific onboarding plan for a new hire, covering accounts, equipment, a buddy, and the first week's activities. Include key contacts, required tool access, and goals for the first 30, 60, and 90 days.

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

• Preparing a checklist before a new hire starts
• Planning Day 1 and the first week
• Setting goals for the first 30, 60, and 90 days

Plan an apprentice's or new laborer's first week so they're useful by Friday and safe from hour one — day-by-day teaching order, the safety non-negotiables stated before anything else, what they're allowed to touch unsupervised, and the check-out conversation that decides week two. Use when a tradesperson says 'my apprentice starts Monday', 'how do I train the new guy', or 'the apprentice is useless and I don't have time to teach'. Produces a first-week plan, a can/can't-touch list, and the Friday review script.

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

Plan a new product launch around finding early customers, guiding their first use, and running short experiments. The skill also helps diagnose stalled adoption, document repeatable outreach methods, and assess whether customer demand supports further expansion.

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

• Finding the first customers for a new product
• Diagnosing weak adoption after launch
• Planning two-week experiments

Summarize recent activity across connected chats, email, documents, and task tools into a daily or weekly digest. See action items first, followed by decisions and updates grouped by project, with duplicate information combined.

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

• Catching up on project activity after time away
• Checking requests and unanswered questions each morning
• Reviewing weekly decisions and document updates

Prepare new hires' onboarding from Google Workspace group records and documented role standards. Plan accounts and memberships, invite hires to Slack channels, and create first-week Linear checklists, while holding Workspace access changes for human approval.

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

• Prepare accounts and first-week tasks before a new hire starts
• Choose groups and Slack channels using role and team standards
• Track account creation and memberships awaiting approval

Create a single onboarding page that helps new employees understand their first week, bringing together a five-day schedule, manager and buddy contacts, learning activities, equipment checks, and clear criteria for being ready.

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

• Preparing a first-week guide for new employees
• Introducing the manager and onboarding buddy
• Organizing learning activities and equipment checks

Help small business owners get started with Claude by guiding two tool connections and trying a task tied to their main concern. Capture business context, suggest relevant skills, and establish a weekly check-in routine.

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

• Start using Claude for business tasks
• Connect tools already used in daily operations
• Save business context and choose initial skills

Check actual OpenRouter charges, API key limits, daily, weekly, and monthly spending, and account credits. Look up a single request by generation ID and report the billed model and provider returned by OpenRouter.

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

• Check daily, weekly, and monthly OpenRouter spending
• See whether an API key is nearing its limit
• Look up a request's billed cost by generation ID

Bring cash, sales, deals, upcoming commitments, and urgent messages into a one-page business brief for small business owners. Use connected tools or owner-supplied figures to show changes, specific risks, and today's most important action.

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

• Checking business performance in a daily brief
• Reviewing weekly results and unresolved issues
• Identifying overdue invoices and stalled deals

Set up recurring tasks in Superset with an agent prompt, a schedule or event trigger, and a chosen execution workspace. After explicit confirmation, create the automation, check its saved settings, and review a real first run.

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

• Scheduling a daily or weekly agent task
• Starting agent work when a GitHub pull request opens
• Triggering tasks from selected Slack reactions

Choose metrics for AI product revenue, sales efficiency, retention, and computing costs. Plan dashboards and weekly reviews, assess customer data quality, and decide how to credit marketing and sales interactions for completed deals.

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

• Choosing revenue and sales metrics for an AI product
• Planning dashboards for executives and sales teams
• Assessing CRM data quality

When you want to manage projects across your businesses using a kanban + Eisenhower methodology. One kanban per business (whatever portfolio of businesses, projects, or initiatives you run). Tool-agnostic — connects via API/MCP to whatever PM tool each business uses (Notion, GitHub Projects, Plane, Linear, Obsidian file-based, or manual mode). Async-first output. Six modes — setup (scaffold a new board for a business), triage (Eisenhower-sort the backlog), next (pick the next thing to work on, single board or across all), status (paste-ready async snapshot), unblock (diagnose Review/Blocked column), weekly (Friday pulse + week planning). Triggers on "/pm," "/pm setup," "/pm triage," "/pm next," "/pm status," "/pm unblock," "/pm weekly," "what should I work on next," "kanban status," "Eisenhower this," "triage my backlog," "what's blocked."

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

Runs once by hand on the first day and once a month after that, on the first weekday, light browser lane. On the first run it researches the business from its own public surfaces before asking anything, writes the strategy folder, seeds the pipeline, reconciles the schedule table, and registers the recurring jobs. On every monthly run it re-reads the evidence the kit produced, applies what changed to the files it owns, and carries every member written setting across verbatim. It holds every outbound action unless you released the channel, and it never enters a credential.

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

Use when the user wants a Xiaohongshu posting calendar, weekly review board, first-10-post launch plan, 10-20-post positioning test, or data-based next-step plan. Trigger phrases: "排期", "复盘", "30 天计划", "前10条", "10-20条测试", "发了没数据", "weekly review", "content calendar", "XHS schedule". Do not use for first-draft editing or initial account positioning.

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

Use when the user wants a Xiaohongshu posting calendar, weekly review board, first-10-post launch plan, 10-20-post positioning test, or data-based next-step plan. Trigger phrases: "排期", "复盘", "30 天计划", "前10条", "10-20条测试", "发了没数据", "weekly review", "content calendar", "XHS schedule". Do not use for first-draft editing or initial account positioning.

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

Win #1 Product of the Day on Product Hunt. Completely reverse-engineered from 30x daily winner and 3x weekly winner campaigns — ranking algorithm decoded, launch timing optimized, hunter selection guide, community engagement approach, and post-launch momentum playbook. Use this if you're: (1) already read PH launch guides but still can't break into Top 5 and need algorithm-level deep optimization, (2) targeting Daily #1 and 5,000+ sign-ups with a proven 30+ case validated approach, or (3) an investor/accelerator coaching portfolio companies on PH launches. What's inside: PH ranking algorithm decoded: weighted factors for first 3 hours, 24 hours, and weekly ranking · Pre-launch preparation: gallery optimization, product URL selection, tagline refinement (≤60 chars) · Launch timing optimization: exact PST launch windows + scheduling guide · Community engagement KPIs: upvote targets, comment response time, maker comment strategy · Platform compliance guide: understanding PH's quality signals and organic growth · Post-launch 72-hour plan: maintaining momentum, conditions for Weekly #1 · Case studies: 3 different categories (AI Tool, App, SaaS) dissected Expected outcomes: Product Hunt Daily #1 ranking · strong community engagement on launch day · 3,000–10,000+ sign-ups (depending on product-market fit) 🇨🇳 Product Hunt 打榜完整攻略 | 🇯🇵 Product Hunt ローンチガイド | 🇰🇷 Product Hunt 런칭 가이드 Keywords: Product Hunt #1, Product Hunt launch strategy, PH ranking algorithm, PH #1 daily winner, Product Hunt tips, product launch, startup launch, ranking optimization, PH gallery optimization, Community engagement strategy, maker community engagement, product strategy, launch tactics, how to win Product Hunt, product hunt best practices

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

Read-only SRE checkup of any GCP project: deterministic probes of the edge, Cloud Run services, 7-day error logs, Cloud Scheduler, alert policies and uptime checks, Secret Manager and IAM, the data stores and the machine's own scheduled jobs, audited into one fixed status table (LIVE / WARNING / RED / INCONCLUSIVE) with evidence, findings by severity, what could not be checked, and a single OVERALL line delivered as one notification. Parametrised by a per-project manifest, so the same routine runs on every project. Use when the operator says "cloud checkup", "SRE check", "is everything live", "what's healthy / warning / red", "any errors this week", "audit the infra", "weekly checkup", "set up the weekly checkup", before a deploy or demo, or after an incident. Cloud Run first; App Engine and GKE differ only in the serving probes.

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

Builds a DRAFT change-communication plan from a change description: audience map, key messages per audience traced to the description, channels, sequence with dates or day offsets, owners, feedback loop and open questions, plus drafts of the first messages for the sponsor to approve. Use when the user asks to "plan the comms for this change", "who needs to hear about this and when", "draft the announcement sequence", "build a communication plan for the rollout", "write the first message to managers about this change" or "how do we tell people about this". Do not use for a clause-by-clause comparison of a changed HR policy with its previous version, use policy-change-briefing instead; for a new hire's first weeks, use onboarding-plan-builder. Drafts for human review; never approves, authorises or signs off.

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

개발 전에 제품의 목적을 검토하고 추진 여부, 첫 사용의 장애물, 기능 우선순위를 정리합니다. 근거와 다음 행동을 담은 기획서나 로드맵을 작성합니다.

• 모호한 아이디어의 기획서 작성
• 개발할 기능의 우선순위 결정
• 출시 전 첫 사용 과정 점검

Create social posts, short video scripts, and weekly content plans for Kortix. Adapt blogs, podcasts, or webinars into standalone pieces suited to LinkedIn, X, Instagram, and TikTok, following the brand’s voice and approved claims.

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

• Drafting LinkedIn posts and X threads
• Repurposing blogs or webinars for social media
• Writing short video scripts

Build a beginner running plan from wherever you are to a real goal — first nonstop mile, 5K, or 10K — that builds up slowly enough to avoid injury. Use when asked for a couch to 5k plan, help me start running, train for a [distance], or a running plan for beginners. Produces a week-by-week walk/run progression to the goal, session detail, pacing and form basics, rest and cross-training, and an injury-prevention note — with a 'check with a doctor if you have health conditions' flag.

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

Operational playbook for running cold email continuously. Prescribes what to do on Monday / Wednesday / Friday / biweekly / monthly / quarterly. Use this as your ongoing cadence once your first campaign is live. What separates hobbyist from top 1% operators isn't tooling — it's consistency. This skill is the schedule.

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

Weekdays, heavy browser lane. Selects the qualified people who have never been written to, drafts each one a first touch into a dated queue file the member reads, and composes each passing draft into the member's own mailbox as an unsent draft. It verifies by the Drafts count and never by a toast. It holds every outbound action unless you released the channel, and it never touches a credential.

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