magnus919/agent-skills

amazon-memo

Create, adapt, or revise Amazon-style narrative decision memos, six-pagers, PR/FAQs, and short decision briefs, including reading meetings and async review.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/magnus919/agent-skills --skill amazon-memo

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Amazon Memo

Help a reader understand a problem, challenge the reasoning, and make or record a decision. Narrative means connected reasoning in prose, not decorative storytelling. Amazon's conventions are a useful starting point; respect the receiving team's own written culture. These are original scaffolds, not official Amazon templates.

When not to use

  • Use adr-authoring for durable architecture decisions and incident-learning

for incident analysis. Add an executive cover memo only when useful; retain the underlying artifact's structure and evidence.

  • Use technical-documentation for instructions and runbooks, writers-helper

for general manuscript craft, and documents for rendered office files.

  • Use product-discovery or product-methodology when the missing work is

understanding the problem or testing demand. A polished memo cannot supply that evidence.

Workflow

  1. Establish the reading contract. Identify the reader, decision or learning

goal, decision owner, deadline, known local conventions, and meeting length or async window. Use supplied context before asking. If a missing detail changes the recommendation, ask one focused question; otherwise state a reasonable assumption and draft. Do not turn intake into an interview by default.

  1. Choose and explain the form in one sentence. Respect an explicitly requested

artifact; explain a mismatch and offer a better fit without silently substituting. Use the routing table below. Read form and length guidance when choosing between forms, planning pages, or adapting to another organization.

  1. Build the argument before polishing. State the customer or stakeholder problem,

relevant baseline, credible alternatives (including continuing as-is), proposed mechanism, costs, risks, uncertainty, and what decision is needed. Separate observed facts, assumptions, forecasts, and invented illustration. Keep citations near claims; identify missing denominators, dates, costs, or sources instead of inventing them. Preserve contradictory findings and explain what they change. With sparse evidence, propose a bounded test or conditional decision rather than a confident rollout. For a test, specify proposed scope, duration or review date, owner, and outcome evidence to inspect. Label unsupplied dates and thresholds as proposals; do not leave the checkpoint as an indefinite request for more evidence.

  1. Draft for this audience. Load only the selected template. Use paragraphs to

connect evidence to consequences. Use headings, compact tables, lists, charts, and appendices when they reduce reader effort; do not turn slides into bullet walls. Define specialist terms for unfamiliar readers and retain precise terms for experts. Keep decision-critical caveats in the body. Templates are starting points; omit irrelevant headings and add what the decision actually needs.

  1. Revise for human reading. Read the revision tests

for every draft or revision. Run the argument, evidence, paragraph, and read-aloud passes. Preserve the writer's voice and legitimate technical language. Revise actual reasoning and sentences; do not use banned-word lists, fixed sentence lengths, made-up readability scores, or synonym swapping as a substitute for judgment.

  1. Design review and closure. For a meeting or async review, read

reading and decision practices. Name the decision owner, reading arrangement, questions to resolve, and where the outcome will live. Allow dissent; do not manufacture consensus. Writing a memo does not authorize sending it, publishing it, or scheduling a meeting.

Form routing

Main reader needDefault form and reasonLoad when drafting
Choose a strategy, resource allocation, staffing plan, or operating changeDecision/strategy narrative: compare choices and consequencesNarrative template
Explore a future customer experience, product, service, or processPR/FAQ: work backwards from value to hard feasibility questionsPR/FAQ template
Decide a narrow, bounded question with limited contextShort decision brief: keep decision overhead proportionateBrief template
Inspect operating results, learn from an incident, approve technical design, or execute a procedureRetain the business-review, incident, design, ADR, or procedure form; add narrative rationale where usefulForm boundaries

Non-negotiable distinctions

  • Six pages is a ceiling, not a requirement. Amazon's 2024 shareholder letter

describes a maximum six-page narrative; do not pad two pages of substance to six. Local rules may differ. No universal font, word count, or heading sequence is established here.

  • A press release is not the whole PR/FAQ. The future release states customer

value; customer and internal FAQs test the proposal. Mark all imagined quotes and future claims as hypothetical. Never present them as testimony or shipped capability.

  • Page estimates are not pagination. Markdown cannot prove a rendered page count.

If actual compliance matters, declare paper size, font, margins, spacing and appendix treatment, then render and inspect. Never shrink type or move essential risks out of the body to make the count fit. Label unrendered lengths as estimates.

when explaining provenance or making claims about a company's practices. Attribute practitioner guidance. Independent written cultures are not presumed Amazon adoptions.

  • Persuasiveness must preserve truth. If asked to make a weak case sound certain,

strengthen the reasoning and state the gaps. Do not inflate demand, suppress counterevidence, invent numbers, or conceal uncertainty.

Supporting material

Read synthetic worked examples when the user needs an illustration or the draft suffers from inflated claims or abstract prose. Every example is invented and generic. Do not reuse personal, client, interview, or confidential material in public examples.

Completion and exit conditions

Deliver the requested draft or revision, a brief form rationale when relevant, material assumptions and evidence gaps, and the review/decision arrangement if requested. Report actual pagination status honestly. For a revision, briefly explain the substantive changes rather than claiming an objective style score.

Stop when the artifact supports its stated reading and decision goal. If evidence cannot support the requested conclusion, deliver a qualified draft or an evidence request with the consequence for the decision. After two non-converging revision passes, name the unresolved audience or argument choice instead of endlessly polishing.

같은 저장소의 Skills

더 많은 Skills

모든 Skills
magnus919
커뮤니티

ai-governance

Design and operate AI governance: principles, decision rights, risk tiers, lifecycle gates, fairness, transparency, privacy, security, compliance mapping, maturity and board reporting across SaaS, API, self-hosted and agentic systems. Use to admit, update or retire Agent Skills, MCP servers and A2A capabilities; approve an agent for production actions; or decide earned-autonomy promotion, reduction or revocation. Cover GxP, ALCOA+, data integrity, electronic records, assurance and QMS interfaces

1시간 설치 수
1
GitHub Stars
172
업데이트
11월 8일
magnus919
커뮤니티

analog-occultism

Use this skill to create subject-neutral images and videos in an analog occultism / industrial CRT noir aesthetic: near-monochrome archival technical atmosphere, severe low-key lighting, tactile signal degradation, industrial geometry, and quiet unresolved tension. Use for portraits, products, environments, interfaces, diagrams, abstract forms, stills, and motion. Do not use for colorful cyberpunk, vaporwave, glossy advertising, conventional horror, or clean digital renders.

1시간 설치 수
1
GitHub Stars
172
업데이트
11월 8일
magnus919
커뮤니티

binary-analysis

Plan static inspection of unknown binary files with a deterministic CLI whose Ghidra operations are currently unimplemented and fail closed. Use when you need to inspect a PE, ELF, or Mach-O file — triage suspicious binaries, map imported APIs, decompile functions, trace call paths, or produce structured evidence reports. Do not use for runtime analysis (debugging, dynamic tracing, sandbox execution), for modifying or patching binaries, or for binaries you already know everything about. The skil

1시간 설치 수
1
GitHub Stars
172
업데이트
11월 8일
magnus919
커뮤니티

brand-designer

Create comprehensive brand identity documentation for any brand. Guides you through documenting strategy, visual identity (logo, color, typography, imagery), voice and tone, customer-centered messaging handoffs, application guidelines, governance, and asset inventory. Produces markdown specs, compiled brand books, and brand-compliant images via reference-image-aware generation. Use when you need to capture a brand's identity in structured, durable form — for vault storage, agency handoff, or pre

1시간 설치 수
1
GitHub Stars
172
업데이트
11월 8일