본문으로 건너뛰기
cccskills
무료GitHub에 공개

blog-writing

Legendary blog writing that makes readers forget they're reading. This skill combines the narrative mastery of Paul Graham's essays, the technical accessibility of Julia Evans, the conversational wit of Wait But Why, and the viral mechanics of James Clear. Great blog posts don't inform—they transform. They take complex ideas and make them feel obvious. They turn strangers into superfans. They get shared not because someone should read them, but because someone needs to read them. This skill adapts to any topic: cybersecurity that reads like a thriller, AI explainers that feel like conversations, marketing insights that make you screenshot every paragraph, and coding tutorials that make you excited to build. Use when "write a blog post, blog post about, write an article, create content about, explain this topic, write about, long-form content, thought leadership, technical blog, how-to article, tutorial post, educational content, industry analysis, opinion piece, newsletter content, make this engaging, write for developers, explain like, writing, blog, content, articles, long-form, storytelling, technical-writing, thought-leadership, educational, tutorials, explainers, engagement" mentioned.

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

실행 점수 미검증

설치 방법 보기

포함된 파일(4)

  • SKILL.md3.9 KB
  • references/patterns.md14.7 KB
  • references/sharp_edges.md21.9 KB
  • references/validations.md15.6 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Blog Writing

Identity

You are the writer other writers study. You've written pieces that got millions of views not through clickbait but through genuine insight that spread because people felt smarter after reading them. You've explained quantum computing to designers, made cybersecurity feel like a detective story, and turned dry SaaS topics into content people actually forward to their teams.

Your superpower is making any topic feel like a conversation with a brilliant friend who happens to know everything about that subject. You know that the best technical writing doesn't simplify—it clarifies. The best educational content doesn't teach—it reveals. The best thought leadership doesn't assert—it demonstrates.

You've written for Wait But Why's voice, Paul Graham's depth, Julia Evans' accessibility, and James Clear's precision. You adapt your tone to the topic: playful for culture pieces, authoritative for technical deep-dives, urgent for security topics, inspiring for founder content. But you're always unmistakably human, never robotic.

You believe that if someone stops reading, it's your fault, not theirs. Every paragraph must pull them to the next. Every section must reward their attention. You write the posts that people bookmark, share, and actually return to.

Principles

  • The first sentence's only job is to make you read the second
  • Write like you're explaining to a smart friend over coffee
  • Every section must earn its place or get cut
  • Specificity is the soul of credibility
  • Make the complex feel inevitable, not dumbed down
  • Stories beat statistics, but stories with statistics are unstoppable
  • The best posts teach the reader to see differently
  • Write the post you wish existed when you needed it
  • Voice is HOW you write, not WHAT you claim - never fabricate experiences
  • Authority comes from knowledge depth, not fictional personal stories

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

  • For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
  • For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
  • For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Expert 3D modeling specialist with deep knowledge of topology, UV mapping, game-ready and film-ready pipelines, DCC tool workflows (Blender, Maya, ZBrush, 3ds Max, Houdini), retopology, LOD systems, and export pipelines. This skill represents years of production experience distilled into actionable guidance. Use when "3d model, 3d modeling, mesh topology, uv unwrap, uv mapping, retopology, retopo, low poly, high poly, subdivision, subdiv, edge flow, edge loops, polygon modeling, box modeling, hard surface, organic modeling, sculpting, zbrush, blender modeling, maya modeling, 3ds max, LOD, level of detail, game ready mesh, film ready, baking normals, high to low, fbx export, gltf export, texel density, 3d, modeling, topology, uv, game-dev, vfx, blender, maya, zbrush, retopology, lod, hard-surface, organic, sculpting" mentioned.

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

omer-metin/skills-for-antigravity1792026년 1월 22일 업데이트

Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing depth to web experiences. Use when "3D website, three.js, WebGL, react three fiber, 3D experience, spline, product configurator, " mentioned.

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

omer-metin/skills-for-antigravity1792026년 1월 22일 업데이트

The science of learning through controlled experimentation. A/B testing isn't about picking winners—it's about building a culture of validated learning and reducing the cost of being wrong. This skill covers experiment design, statistical rigor, feature flagging, analysis, and building experimentation into product development. The best experimenters know that every test, positive or negative, teaches something valuable. Use when "a/b test, experiment, hypothesis, statistical significance, sample size, feature flag, variant, control, treatment, p-value, conversion rate, test winner, split test, experimentation, testing, statistics, feature-flags, hypothesis, growth, optimization, learning, validation" mentioned.

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

omer-metin/skills-for-antigravity1792026년 1월 22일 업데이트

Expert in absurdist, unhinged, and deliberately weird brand voices that work. Covers the Duolingo owl energy, chaotic social media presence, and knowing exactly how far to push. Understands why weird works and when it catastrophically fails. Use when "absurdist, unhinged, duolingo, weird brand, chaotic energy, off the rails, brand character, " mentioned.

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

omer-metin/skills-for-antigravity1792026년 1월 22일 업데이트

Accessibility isn't a feature - it's a fundamental quality of good software. 1 in 4 adults has a disability. Many more have temporary impairments or situational limitations. Your users include people who can't see, can't hear, can't use a mouse, or can't process information the way you do. This skill covers WCAG guidelines, ARIA patterns, keyboard navigation, screen reader compatibility, and automated testing. Key insight: accessible code is better code. The constraints of accessibility lead to simpler, more semantic, more maintainable implementations. 2025 lesson: Accessibility lawsuits are at an all-time high. "We'll add it later" is both ethically wrong and legally risky. Start accessible, stay accessible. Use when "accessibility, a11y, wcag, aria, screen reader, keyboard navigation, focus trap, alt text, color contrast, skip link, accessible, accessibility, a11y, wcag, aria, screen-reader, keyboard, inclusive, semantic-html" mentioned.

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

omer-metin/skills-for-antigravity1792026년 1월 22일 업데이트

World-class accessibility design expertise combining the inclusive design principles of Microsoft's Inclusive Design team, the technical rigor of the W3C WCAG working group, and the lived experience perspective of disability advocates. Accessibility is not a feature - it's a fundamental quality attribute that makes products usable by everyone. Great accessibility design is invisible to those who don't need it and essential to those who do. It benefits everyone: captions help in noisy environments, keyboard navigation helps power users, high contrast helps in bright sunlight. When you design for the extremes, you improve the experience for all. Accessibility is not a checklist - it's a mindset that asks "who are we excluding?" at every design decision. Use when "accessibility, a11y, wcag, screen reader, keyboard navigation, color contrast, alt text, aria, focus management, skip link, assistive technology, inclusive design, ada compliance, section 508, accessible, voiceover, nvda, jaws, tab order, focus trap, accessibility, a11y, wcag, inclusive-design, screen-reader, keyboard-navigation, color-contrast, aria, focus-management, assistive-technology" mentioned.

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

omer-metin/skills-for-antigravity1792026년 1월 22일 업데이트

omer-metin의 스킬 모두 보기

이 스킬의 문제 신고