affaan-m/ecc

messages-ops

Evidence-first live messaging workflow for ECC.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/affaan-m/ecc --skill messages-ops

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

Messages Ops

Use this when the task is live-message retrieval: iMessage, DMs, recent one-time codes, or thread inspection before a follow-up.

This is not email work. If the dominant surface is a mailbox, use email-ops.

Skill Stack

Pull these ECC-native skills into the workflow when relevant:

  • email-ops when the message task is really mailbox work
  • connections-optimizer when the DM thread belongs to outbound network work
  • lead-intelligence when the live thread should inform targeting or warm-path outreach
  • knowledge-ops when the thread contents need to be captured into durable context

When to Use

  • user says "read my messages", "check texts", "look in DMs", or "find the code"
  • the task depends on a live thread or a recent code delivered to a local messaging surface
  • the user wants proof of which source or thread was inspected

Guardrails

  • resolve the source first:
  • local messages
  • X / social DM
  • another browser-gated message surface
  • do not claim a thread was checked without naming the source
  • do not improvise raw database access if a checked helper or standard path exists
  • if auth or MFA blocks the surface, report the exact blocker

Workflow

1. Resolve the exact thread

Before doing anything else, settle:

  • message surface
  • sender / recipient / service
  • time window
  • whether the task is retrieval, inspection, or prep for a reply

2. Read before drafting

If the task may turn into an outbound follow-up:

  • read the latest inbound
  • identify the open loop
  • then hand off to the correct outbound skill if needed

3. Handle codes as a focused retrieval task

For one-time codes:

  • search the recent local message window first
  • narrow by service or sender when possible
  • stop once the code is found or the focused search is exhausted

4. Report exact evidence

Return:

  • source used
  • thread or sender when possible
  • time window
  • exact status:
  • read
  • code-found
  • blocked
  • awaiting reply draft

Output Format

text
SOURCE
- message surface
- sender / thread / service

RESULT
- message summary or code
- time window

STATUS
- read / code-found / blocked / awaiting reply draft

Pitfalls

  • do not blur mailbox work and DM/text work
  • do not claim retrieval without naming the source
  • do not burn time on broad searches when the ask is a recent-code lookup
  • do not keep retrying a blocked auth path without surfacing the blocker

Verification

  • the response names the message source
  • the response includes a sender, service, thread, or clear blocker
  • the final state is explicit and bounded

Tâches connexes

du même dépôt

Autres Skills

Tous les Skills
affaan-m
Communauté

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.

Installations / 24h
489
GitHub Stars
308,2 k
Mis à jour
20 nov.
affaan-m
Communauté

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.

Installations / 1h
5
GitHub Stars
308,2 k
Mis à jour
20 nov.
affaan-m
Communauté

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.

Installations / 1h
2
GitHub Stars
307,9 k
Mis à jour
20 nov.
affaan-m
Communauté

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.

Installations / 1h
2
GitHub Stars
307,9 k
Mis à jour
20 nov.