「letter」の検索結果

Use this skill when a user asks to polish, rewrite, humanize, de-AI, localize, or oralize Chinese writing, including short-video scripts, articles, social posts, speeches, newsletters, and personal-IP content. The skill diagnoses “AI味”, preserves the user's meaning, adapts to optional style samples, replaces translation-like phrasing with natural Chinese expression, and outputs a polished version plus concise revision notes.

日本語の概要は準備中です。原文の説明を表示しています。

Scrub English drafts for AI tells before publishing. Use for any English LinkedIn post or newsletter draft right after composition and BEFORE export. Removes em-dash-as-pause, weak hedges, rule-of-three patterns, AI vocabulary, negative parallelisms, and inflated symbolism. Triggers on "polish", "humanize", "make this sound human", "/polisher", or after any English composer output. Leaves Arabic and Hebrew drafts untouched — humanizer-* skills handle those.

日本語の概要は準備中です。原文の説明を表示しています。

Produce a weekly digest of what Ahmad saved in OpenMark over a given time window, clustered by topic. Use whenever Ahmad asks "what did I save this week", "what's new in OpenMark", "last week's saves", "this week's bookmarks", "what happened in my feed", "weekly recap", or any temporal summary of saved content. Faster than full newsletter — output is a scannable digest, not a published post. Triggers on "this week", "last week", "what's new", "weekly digest", "recent saves", "recap".

日本語の概要は準備中です。原文の説明を表示しています。

Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credib...

日本語の概要は準備中です。原文の説明を表示しています。

Work the review of a research run with rs_review — read the manuscript and record the panel's concerns with the evidence that grounds each one, keep the author's reply and the re-review's finding in their separate columns, run the devil's advocate with the concession threshold the tool enforces, and write the panel report and traceability matrix a response-to-reviewers letter is built from. Use when a document is ready for review, when a concern has to be answered or re-reviewed, or when an attack or a concession is being recorded.

日本語の概要は準備中です。原文の説明を表示しています。

Specialist for the entire job application process. Analyzes job postings, optimizes profiles (LinkedIn/CV), and generates tailored cover letters. Generates ASCII CVs from a SQLite database and folder structure. cv_generator.py is ported standalone -- no BACH runtime required.

日本語の概要は準備中です。原文の説明を表示しています。

Use whenever several decisions are pending or have accumulated -- whether within a topic, project, document, or over the course of a session: inventory them, present a numbered briefing with options A/B/C/D and a marked recommendation, accept letter answers (including batches), record the results, and write them back into the source documents.

日本語の概要は準備中です。原文の説明を表示しています。

Builds a DRAFT content calendar for a stated period from the themes, channels, cadence rules, fixed dates and owners the user provides: one dated row per planned item with theme, channel, format, working title, owner, status and source, plus a cadence check with its arithmetic, theme balance, owner load and the slots left open. Use when the user asks to "build the content calendar for Q4", "lay these themes onto dates", "plan a month of posts across our channels", "extend the editorial calendar" or "check this calendar against our cadence". Do not use for deciding what the campaign says or why it runs, use campaign-brief-builder instead; for writing the items themselves, use announcement-drafter or internal-newsletter-drafter. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Drafts one internal or external announcement (email, intranet post, town hall script, customer notice or press statement) in the organisation's voice from the facts, audience, sender and style guide the user provides, with a fact trace, reader-questions check, pre-send checks and an approvals checklist left blank for the named approvers. Use when the user asks to "announce this change to all staff", "draft the customer notice", "write the town hall script", "prepare a holding statement" or "rewrite this in our voice". Do not use for a digest of several items, use internal-newsletter-drafter instead; to pre-test a drafted message against personas, use communication-pretest-panel. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Write an evergreen teaching longform for non-technical readers built from your own real material (systems you run, dated failures, numbers), structured as a stitched lesson that can live as a blog post, a GitHub guide hub and a newsletter issue. Use when turning lived engineering experience into a durable how-to. Triggers: /guide, make a guide, build a lesson, evergreen guide.

日本語の概要は準備中です。原文の説明を表示しています。

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks to "build a media list for my launch", "write a launch press release", or "pitch press under embargo"; produces a three-tier media and analyst list (Tier 1 exclusive candidates, Tier 2 vertical press, Tier 3 communities and newsletters), an embargo pitch timing skeleton keyed to the launch-registry date, a press-release draft in standard structure with no fabricated quotes or numbers, and an analyst briefing outline. Not for press-kit assets — use launch-asset-packager; not for follow-up sequence mechanics — use outreach-manager; not for post-launch news-echo monitoring — use launch-monitor. 媒体名单/禁运期pitch/新闻稿/分析师简报

日本語の概要は準備中です。原文の説明を表示しています。

Build messaging applications using Azure Service Bus SDK for JavaScript (@azure/service-bus). Use when implementing queues, topics/subscriptions, message sessions, dead-letter handling, or enterpri...

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Aws Lambda Deep — deep AWS Lambda analysis covering function inventory, cold start profiling, memory optimization, concurrency patterns, layer dependency auditing, dead letter queue health, event source mappings, and cost estimation. Goes beyond basic metrics to identify optimization opportunities.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Aws Sqs — aWS SQS queue metrics, dead letter queue management, SNS subscription management, message attributes, and queue health monitoring.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Aws Eventbridge — aWS EventBridge event bus management, rule analysis, target health monitoring, and schema registry exploration. Covers event pattern matching, rule invocation metrics, dead-letter queue analysis, cross-account event routing, and event replay.

日本語の概要は準備中です。原文の説明を表示しています。

Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.

日本語の概要は準備中です。原文の説明を表示しています。

Serverless form handling on Netlify-hosted sites — detects HTML forms at deploy time, stores submissions, filters spam, and sends notifications. Use when adding a contact form, lead-capture form, file-upload form, or newsletter signup to a Netlify site; wiring AJAX form submission; setting up a custom thank-you page; adding a honeypot or reCAPTCHA to a form; getting forms working in Next.js, Nuxt, SvelteKit, Astro, or Gatsby; reading form submissions via the Netlify API; or debugging missing submissions and forms that silently fail to register.

日本語の概要は準備中です。原文の説明を表示しています。

Use when someone asks to write, rewrite, review, or improve text that appears inside a product or interface. Examples: "review the UX copy", "is there a better way to phrase this", "rewrite this error message", "write copy for this screen/flow/page", reviewing button labels, improving CLI output messages, writing onboarding copy, settings descriptions, or confirmation dialogs. Trigger whenever the request involves wording shown to end users inside software — apps, web, CLI, email notifications, modals, tooltips, empty states, or alerts. Also trigger for vague requests like "review the UX" where interface copy review is implied. Do NOT trigger for content marketing, blog posts, app store listings, API docs, brand guides, cover letters, or interview questions — this is a technical writing skill for interface language.

日本語の概要は準備中です。原文の説明を表示しています。

Create a company-specific job application package from a JD, resume.md, cover letter drafts, HR review, and optional company values input. Use when the user wants 지원 패키지, submission checklist, application folder structure, final answer snippets, email draft support, or safe pre-submission preparation without automatic final submission.

日本語の概要は準備中です。原文の説明を表示しています。

Build or improve a job seeker's resume.md source file from conversational career input. Use when the user wants to create resume.md, organize new-grad or experienced career history, convert raw experiences into STAR/CAR evidence, add missing metrics, or prepare reusable career evidence for cover letters and job applications. 한국어 요청도 포함합니다 - 이력서 작성, 이력서 정리, 경력기술서, 경력 정리, 커리어 정리, 자소서 소재 정리, 내 경험 정리해줘, 신입 이력서, 경력직 이력서.

日本語の概要は準備中です。原文の説明を表示しています。

Review resumes, cover letters, application packages, and evidence maps from an HR perspective. Use when the user asks for 자기소개서 리뷰, 자소서 검토, HR 검토, 제출 전 점검, unsupported-claim detection, company-name residue checks, or risk-focused revision advice before applying.

日本語の概要は準備中です。原文の説明を表示しています。

Use when: writing or reviewing cover letters, recruiter email replies, LinkedIn outreach, or interview follow-ups. Removes AI-template patterns and writes with a specific, confident, human voice.

日本語の概要は準備中です。原文の説明を表示しています。

Use when: reviewing or producing any external-facing prose — ADRs, proposals, GitHub comments, Telegram messages, cover letters, client drafts, or planner-mode wording. Removes AI-tell patterns and raises writing quality before output leaves the team.

日本語の概要は準備中です。原文の説明を表示しています。