affaan-m/ecc

content-engine

Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns.

소스 보기

사용 방법

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

시작 전 확인

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

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

Content Engine

Build platform-native content without flattening the author's real voice into platform slop.

When to Activate

  • writing X posts or threads
  • drafting LinkedIn posts or launch updates
  • scripting short-form video or YouTube explainers
  • repurposing articles, podcasts, demos, docs, or internal notes into public content
  • building a launch sequence or ongoing content system around a product, insight, or narrative

Non-Negotiables

  1. Start from source material, not generic post formulas.
  2. Adapt the format for the platform, not the persona.
  3. One post should carry one actual claim.
  4. Specificity beats adjectives.
  5. No engagement bait unless the user explicitly asks for it.

Source-First Workflow

Before drafting, identify the source set:

  • published articles
  • notes or internal memos
  • product demos
  • docs or changelogs
  • transcripts
  • screenshots
  • prior posts from the same author

If the user wants a specific voice, build a voice profile from real examples before writing. Use brand-voice as the canonical workflow when voice consistency matters across more than one output.

Voice Handling

brand-voice is the canonical voice layer.

Run it first when:

  • there are multiple downstream outputs
  • the user explicitly cares about writing style
  • the content is launch, outreach, or reputation-sensitive

Reuse the resulting VOICE PROFILE here instead of rebuilding a second voice model. If the user wants Affaan / ECC voice specifically, still treat brand-voice as the source of truth and feed it the best live or source-derived material available.

Hard Bans

Delete and rewrite any of these:

  • "In today's rapidly evolving landscape"
  • "game-changer", "revolutionary", "cutting-edge"
  • "here's why this matters" unless it is followed immediately by something concrete
  • ending with a LinkedIn-style question just to farm replies
  • forced casualness on LinkedIn
  • fake engagement padding that was not present in the source material

Platform Adaptation Rules

X

  • open with the strongest claim, artifact, or tension
  • keep the compression if the source voice is compressed
  • if writing a thread, each post must advance the argument
  • do not pad with context the audience does not need

LinkedIn

  • expand only enough for people outside the immediate niche to follow
  • do not turn it into a fake lesson post unless the source material actually is reflective
  • no corporate inspiration cadence
  • no praise-stacking, no "journey" filler

Short Video

  • script around the visual sequence and proof points
  • first seconds should show the result, problem, or punch
  • do not write narration that sounds better on paper than on screen

YouTube

  • show the result or tension early
  • organize by argument or progression, not filler sections
  • use chaptering only when it helps clarity

Newsletter

  • open with the point, conflict, or artifact
  • do not spend the first paragraph warming up
  • every section needs to add something new

Repurposing Flow

  1. Pick the anchor asset.
  2. Extract 3 to 7 atomic claims or scenes.
  3. Rank them by sharpness, novelty, and proof.
  4. Assign one strong idea per output.
  5. Adapt structure for each platform.
  6. Strip platform-shaped filler.
  7. Run the quality gate.

Deliverables

When asked for a campaign, return:

  • a short voice profile if voice matching matters
  • the core angle
  • platform-native drafts
  • posting order only if it helps execution
  • gaps that must be filled before publishing

Quality Gate

Before delivering:

  • every draft sounds like the intended author, not the platform stereotype
  • every draft contains a real claim, proof point, or concrete observation
  • no generic hype language remains
  • no fake engagement bait remains
  • no duplicated copy across platforms unless requested
  • any CTA is earned and user-approved

Related Skills

  • brand-voice for source-derived voice profiles
  • crosspost for platform-specific distribution
  • x-api for sourcing recent posts and publishing approved X output

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
affaan-m
커뮤니티

rust-testing

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology. Use when writing Rust tests — unit, integration, async, property-based, or coverage.

24시간 설치 수
489
GitHub Stars
30.8만
업데이트
11월 20일
affaan-m
커뮤니티

search-first

Research-before-coding workflow: search npm/PyPI, MCP servers, skills, and GitHub for existing tools before writing custom code, then adopt, extend, or build. Launches the researcher agent for non-trivial needs. Use when starting a feature, adding a dependency or integration, or about to write a utility that may already exist.

1시간 설치 수
5
GitHub Stars
30.8만
업데이트
11월 20일
affaan-m
커뮤니티

browser-qa

Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP / DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before shipping frontend changes, reviewing a frontend PR, or checking responsive layout and accessibility.

1시간 설치 수
2
GitHub Stars
30.8만
업데이트
11월 20일
affaan-m
커뮤니티

docker-patterns

Docker and Docker Compose patterns for local development, hardened CLI installer harnesses, container security, networking, volumes, and multi-service orchestration. Use when creating or reviewing Dockerfiles and Compose services, testing installers across Linux distributions, or planning accurate native macOS and Windows validation.

1시간 설치 수
2
GitHub Stars
30.8만
업데이트
11월 20일