「clarity」の検索結果

Ultra-compressed response style that reduces output token count while preserving technical accuracy, with intensity levels and auto-clarity safety rules

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

Help users master professional writing to bridge gaps between stakeholders, scale their leadership influence, and ensure organizational clarity through structured narratives and async-first norms.

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

Help users design high-performing product and engineering organizations by choosing the right reporting models, team sizes, and cross-functional partnerships. It focuses on reducing friction and maximizing ownership through structural clarity.

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

Help users master the high-stakes communication required to navigate executive reviews, board meetings, and strategic decision-making with clarity and confidence.

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

Use when building or revising exhibits for an American Economic Journal: Macroeconomics (AEJ: Macro) manuscript — impulse-response figures, fan charts, model-fit overlays, and regression/moment tables — to AEA house standards and macro conventions. Formatting and clarity; it does not generate the underlying estimates.

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

Use when revising prose, the abstract, or the introduction of an American Economic Journal: Macroeconomics (AEJ: Macro) manuscript for AEA house style and the broad-interest macro arc. Late-stage polish on framing and clarity; it does not fix identification, the model, or exhibits.

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

Polish mathematical modeling paper drafts for grammar, clarity, formula consistency, hedging calibration, overclaim detection, and contest formatting compliance. Use after paper-section-writer has drafted sections.

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

The Jobs-to-be-Done framework as applied product methodology. Job statements, struggling moments, hire and fire criteria, the difference between feature-thinking and job-thinking. Honest about where JTBD adds clarity (discovery, prioritization, positioning) and where it becomes performative ritual (job-statement workshops that do not drive decisions, persona-theater disguised as JTBD). Triggers on jobs-to-be-done, JTBD, job statements, struggling moments, hire criteria, fire criteria, switch triggers, functional emotional social jobs, outcome-driven innovation. Also triggers when a team is over-relying on feature-request lists or persona archetypes that do not drive product decisions, when a positioning conversation needs the framing JTBD provides, or when discovery is producing outputs that do not connect to product strategy.

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

Pre-publish QA framework for content. Brief adherence, voice consistency, fact accuracy, structure and clarity, AI-content audit, SEO and AEO compliance, internal linking and schema validation, QA at scale via sampling, the QA workflow, and the discipline that distinguishes catch-problems QA from checkbox QA. Triggers on editorial QA, content review, pre-publish review, content audit, content QA process, AI-content audit, hallucination check, content sampling, programmatic QA, voice consistency check, brief adherence check. Also triggers when a content team is shipping sloppy work, when AI-co-authored content is reaching publish unaudited, when a QA process burns reviewers out, or when a programmatic SEO set needs sampling discipline. On a voice consistency check, this skill owns checking a draft against an existing voice system at the publish gate; use `brand-voice` when the voice system itself needs defining or documenting.

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

Analyze prompts for clarity, structure, examples, and output reliability

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

Systematic copy editing through focused passes (the Seven Sweeps Framework) covering clarity, voice, proof, specificity, and friction removal. Use when editing marketing copy, reviewing drafts, polishing content, or proofreading.

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

Landing page and marketing page conversion rate optimization covering value proposition clarity, headline effectiveness, CTA hierarchy, visual flow, social proof placement, objection handling, and structured A/B testing.

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

Apply elite legal writing techniques drawn from Justice Kagan, Boies & Olson, and other top advocates to any legal document — briefs, submissions, letters, opinions, memos, or persuasive correspondence. This skill covers both prose craft (clarity, examples, parallel construction, voice, quoting) and architectural strategy (argument sequencing, framing, openings, endings). Use this skill whenever the user asks you to draft, edit, or improve legal writing and wants it to be genuinely persuasive — not just correct. Also trigger when the user mentions 'make it more persuasive', 'sharpen this', 'strengthen the argument', 'rewrite this section', 'punch it up', 'legal writing', 'draft a brief', 'draft a submission', 'write like a top advocate', or asks you to improve the rhetoric, flow, or force of any legal document. This skill complements the larissa-legal-voice skill (which handles tone and personal voice) by adding the persuasive technique layer on top.

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

Rigorous multi-pass editor for law review articles, student notes, seminar papers and other legal scholarship. Runs six specialized passes — structure, substantive critique, Bluebook citations, grammar and clarity, fact-checking against sources, and a synthesizing memo — and delivers an editorial memo with issues prioritized as critical, substantial or minor and keyed to specific footnotes and paragraphs. Handles articles of any length, including 50,000-word pieces, by chunking on section boundaries. Reads .docx directly. Use when editing, critiquing, workshopping or pre-submission-reviewing academic legal writing. Triggers on "edit my article," "review this draft," "critique my note," "check my Bluebook citations," "is my argument sound," "read my law review piece," "workshop this paper," "pre-submission review." Chunking needs Python 3; fact-checking needs web search; both degrade gracefully without.

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

Line-by-line copy editing and improvement for marketing content. Polish existing copy for clarity, conciseness, impact, and conversion. Trigger phrases: "edit my copy", "improve this copy", "polish this text", "copy edit", "make this clearer", "tighten this up", "proofread", "review my copy", "make this more persuasive", "fix my writing".

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

Plan, triage, and write academic rebuttals and review responses. Use when an AI research agent needs to handle conference, journal, workshop, or grant reviews; classify reviewer concerns; decide what evidence or experiments can change the decision; write an AC-facing executive summary; draft per-reviewer responses; correct factual misunderstandings without sounding hostile; handle novelty, baseline, method, experiment, clarity, and scope objections; or produce a final rebuttal checklist.

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

Requirements quality critique dimensions for peer review - confirmation bias detection, completeness validation, clarity checks, testability assessment, and priority validation

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

Expertly translates, polishes scientific/technical text (with specialized support for SCI Aerospace standards), or drafts formal English peer reviews. Ensures accuracy, clarity, and adherence to high academic standards.

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

Improves the quality of images, especially screenshots, by enhancing resolution, sharpness, and clarity. Perfect for preparing images for presentations, documentation, or social media posts.

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

Edit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improve an article draft.

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

Post-run self-evaluation system that scores agent output on correctness, clarity, actionability, and conciseness. Use after /team runs, skill executions, or when explicitly asked to evaluate output quality.

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

Clean-code engineering standards for writing, refactoring, and reviewing code in any programming language. Use this whenever the user asks to write clean code, follow clean-code principles, refactor for clarity, improve naming, reduce complexity or duplication, separate concerns, tighten error handling, work test-first or do TDD, or otherwise raise code quality, readability, and maintainability. Also use when writing or reviewing Operately APIs or Ecto queries. Apply these rules by default when producing or changing code for a quality-conscious user.

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

Write maintainable Python with small functions, explicit boundaries, guard clauses, and readable state flow. Use when refactoring Python services, helpers, modules, or async logic for clarity—not generic test writing, tooling setup, or database transaction implementation.

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

Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Advisory only.

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