Plan & spec
10,746 rows, by stacks then stars
2,010 of these skill files have been read, by 1,360 distinct authors, and what they tell an agent counted. What Plan & spec authors agree on, and what they forbid
the-nam-shub/e5-real-skills/skills/paid-media-strategy Skill
no license8★ repoComprehensive guidance for planning, executing, and optimizing B2B paid media campaigns across search, social, display, CTV, OOH, and ABM channels — trigger when a user needs help with paid advertising strategy, channel selection, budget allocation, creative approach, audience targeting, or campaign measurement.
the-nam-shub/e5-real-skills/skills/podcast-strategy Skill
no license8★ repoGuides marketers through B2B podcast strategy decisions including launch approach, format, guest sourcing, content repurposing, and ROI measurement; trigger when a user is planning, launching, or optimizing a B2B podcast.
the-nam-shub/e5-real-skills/skills/presentation-strategy Skill
no license8★ repoGuidance for structuring, developing, and delivering effective presentations — from conference talks to board meetings — covering audience analysis, talk architecture, delivery mindset, and slide strategy.
the-nam-shub/e5-real-skills/skills/pricing-page-strategy Skill
no license8★ repoGuidance for building, auditing, and optimizing B2B SaaS pricing pages to improve clarity, conversion, and prospect self-qualification. Trigger when a user asks about pricing page design, structure, copy, CTAs, or whether to show pricing publicly.
the-nam-shub/e5-real-skills/skills/pricing-strategy Skill
no license8★ repoGuides Claude to help B2B marketers build, communicate, and optimize pricing strategy — covering value metrics, pricing page design, organizational structure, and value-based frameworks
the-nam-shub/e5-real-skills/skills/product-launch-strategy Skill
no license8★ repoGuidance for planning, structuring, and executing B2B product launches — from cadence and cross-functional alignment to messaging, distribution, and post-launch iteration. Trigger when a user is preparing a product launch, defining a launch calendar, or building a go-to-market process around product releases.
the-nam-shub/e5-real-skills/skills/rebrand-strategy Skill
no license8★ repoGuides marketers through planning and executing a B2B company rebrand, from securing CEO buy-in and setting timelines to managing post-launch adoption — trigger when a user is scoping, pitching, or executing a rebrand initiative.
the-nam-shub/e5-real-skills/skills/sales-led-gtm-strategy Skill
no license8★ repoGuidance for structuring go-to-market strategy in sales-led B2B organizations, including how to align marketing tactics to longer sales cycles and higher-intent buyer behavior
Social media strategy and operations
the-nam-shub/e5-real-skills/skills/social-media-strategy-and-operations Skill
no license8★ repoGuides B2B marketers through social media strategy decisions, channel selection, content operations, posting cadence, measurement, and platform-specific best practices. Trigger when a user asks about social media planning, content creation workflows, channel prioritization, organic vs. paid tradeoffs, or platform-specific tactics.
the-nam-shub/e5-real-skills/skills/sponsorship-strategy Skill
no license8★ repoGuides Claude in helping B2B marketers evaluate, structure, and execute sponsorship programs—whether buying sponsorships as an advertiser or selling them as a media/event operator
the-nam-shub/e5-real-skills/skills/visual-content-strategy Skill
no license8★ repoGuides Claude in advising marketers on how to select, prioritize, and deploy visuals on product and landing pages to support messaging and drive conversion
the-nam-shub/e5-real-skills/skills/webinar-strategy Skill
no license8★ repoHelps B2B marketers plan, promote, run, and repurpose webinars — covering topic selection, format, length, attendance mechanics, follow-up, and content distribution. Trigger when a user is designing a webinar program, troubleshooting low attendance, or deciding how to structure a live session.
amaynez/bulletproof-business-plan/skills/bullet-proof-business-plan Skill
no license8★ repoStress-test and strengthen a business plan through iterative rounds of adversarial investor critique and strategic re-engineering. Use when you need to identify existential risks in a business model and transform vulnerabilities into defensible moats. Do NOT use for creative writing, general notes, or non-business strategies.
anmolnagpal/devops-skills/skills/deploy Skill
8★ repoDeployment strategy, production-readiness gating, and rollback planning for AWS/EKS services. Use when user says 'how should I deploy this', 'blue-green or canary', 'are we ready to ship', 'production readiness', 'plan a rollback', 'pre-deploy check', or before a first production release. Pairs with /k8s, /ci, /github-actions, /tf which own the per-artifact checks.
ontology-of-everything/SemanticSkills/skills/huawei-cloud-cost-estimation Skill
8★ repoSemantic agent skills for cloud operations — open SKILL.md packages for Claude Code, Cursor, Codex CLI. Includes huawei-cloud-billing-scout (read-only BSS/KooCLI billing).
kensaurus/cursor-kenji/skills/audit-realworld Skill
8★ repoAudit a full-stack app against the RealWorld ("Conduit") reference — its formal API spec, shared Bruno/Hurl E2E suite, and closest-stack reference implementation — to find what is implemented correctly, partially, or not at all across frontend, backend, and data layer. Auto-detects whether to run strict spec conformance (the repo IS a RealWorld build) or benchmark the repo's own domain against RealWorld's production-relevant patterns, and bows out cleanly on non-CRUD/non-web repos. Read-only: produces a prioritized gap report and hands remediation to other skills. Use when "audit against realworld", "compare my app to realworld", "conduit conformance", "is my full-stack app complete", "full-stack gap check", or "what's missing to reach production". RealWorld is a completeness/pattern reference, not a production bar — real hardening is delegated to audit-security / plan-* skills.
kensaurus/cursor-kenji/skills/audit-ux-journeys Skill
8★ repoCross-page UX audit for user stories, task completion, and information architecture — the layer audit-ux (per-page heuristics) doesn't cover. Derives real user stories from routes/nav/CTAs (not invented personas), scopes depth by audit trigger (KPIs dropping / complaints / redesign / pre-launch), audits IA structurally (click depth, orphan pages, dead ends, label consistency, grouping vs mental model, findability/first-click), then walks every core story end-to-end in a headed browser producing a task-completion matrix with friction logs. Evidence-disciplined: validates with analytics/funnels/drop-offs when available, otherwise marks findings as expert-judgment hypotheses — never presents taste as data. Reports impact×effort quick-wins vs roadmap. Use when "audit user flows", "user story audit", "information architecture / IA audit", "can users find X", "users get lost", "navigation audit", "funnel drop-off", "task completion", or "audit-ux-journeys". Per-page heuristics/microcopy stay with audit-ux.
kensaurus/cursor-kenji/skills/design-api Skill
8★ repoDesign RESTful and GraphQL APIs following current best practices for naming, versioning, error shapes, and auth patterns. Use when the user says "design an API", "create endpoints", "structure my API responses", "plan API architecture", "REST vs GraphQL", or "API contract". Covers OpenAPI spec, pagination, rate limiting, and backwards-compatible evolution. Pairs with backend-patterns, audit-security.
kensaurus/cursor-kenji/skills/design-prd Skill
8★ repoGenerate Product Requirements Documents through structured conversation for any project. Auto-detects tech stack, existing features, and data model from the codebase. Uses Firecrawl to research competitor products and UX patterns, Context7 to check framework capabilities for feasibility, and Supabase MCP to verify data model feasibility. Produces actionable PRDs with technical feasibility sections informed by real codebase analysis. Use when starting a new feature, documenting requirements, creating specs before implementation, or needing clarity on scope and success criteria.
kensaurus/cursor-kenji/skills/plan-aeo-readiness Skill
8★ repoAudit a site for answer-engine and generative-engine visibility (citation by ChatGPT, Claude, Perplexity, AI Overviews), then produce a phased improvement plan. Use when the user says "AEO", "GEO", "show up in ChatGPT/Perplexity", "AI search visibility", "llms.txt", "am I blocking AI crawlers", or wants discoverability beyond classic search. Audits AI-crawler access, SSR vs JS-hidden content, llms.txt, structured schema, and direct-answer-first structure. Plan only until approved. Pairs with enhance-web-seo, docs-writer, plan-antislop. Do NOT use for Core Web Vitals alone (enhance-web-seo).
kensaurus/cursor-kenji/skills/plan-antislop Skill
8★ repoAudit a codebase, UI, or copy for machine-generated tells across prose, visual/UI, code, and structure/IA, then produce a phased de-slop burndown. Use when the user says "feels AI-generated", "looks like AI slop", "reads like ChatGPT", "feels generic/soulless", or wants an authenticity/voice pass before launch. Plan only — nothing rewritten until each phase is approved. Pairs with enhance-web-ux, enhance-web-landing, design-frontend. Do NOT use for functional bugs (debug-*), security (plan-security-audit), or net-new design.
kensaurus/cursor-kenji/skills/plan-capacitor-hardening Skill
8★ repoAudit a Capacitor/Ionic hybrid app for native-layer security gaps, then produce a phased hardening plan. Use when the user says "is my Capacitor app secure", "harden my hybrid app", "WebView security", "secure token storage", "deep link OAuth", "cleartext traffic", "exported activity", or is hardening before store submission. Audits four pillars: Data, Auth/Deep-Linking, Network, WebView, plus OTA vs store policy. Plan only until approved. Pairs with plan-secrets-audit, plan-mobile-readiness, mobile-capacitor-platform. Do NOT use for UI polish or React Native perf.
kensaurus/cursor-kenji/skills/plan-data-integrity Skill
8★ repoAudit a project for destructive-operation and migration safety gaps, then produce a phased safeguard plan. Use when the user says "is my migration safe", "could I lose data", "check my backups", "my agent might delete prod", "safe schema changes", or "disaster recovery". Audits unguarded DELETE/TRUNCATE/DROP, column drops without backfill, backups in prod blast radius, and over-scoped agent/CI tokens. Plan only until approved. Pairs with plan-rls-audit, audit-db-schema, db-migrator. Do NOT use for query perf or RLS alone.
kensaurus/cursor-kenji/skills/plan-dependency-provenance Skill
8★ repoAudit dependencies for hallucinated or slopsquatted packages, supply-chain risk, and licensing/provenance gaps, then produce a phased remediation plan. Use when the user says "check my dependencies", "is this package real", "slopsquatting", "audit my supply chain", "license check", "SBOM", or "did the AI hallucinate a package". Audits package existence/age/popularity, lockfile integrity, typo-squatted names, transitive bloat, and license provenance. Plan only until approved. Pairs with plan-secrets-audit, workflow-housekeep. Do NOT use for version bumps or bundle size (audit-bundle-size).
kensaurus/cursor-kenji/skills/plan-docs-sync Skill
8★ repoAudit documentation against actual code behavior and plan corrections — no rewrites in this pass. Drift taxonomy (stale, missing, phantom, contradictory, onboarding-breaking, inline rot, API-contract drift) with code-as-source-of-truth methodology. Onboarding-drift checks against .env.example and CLI --help; docs-as-code guardrails for same-PR updates. Docs describe real current behavior — never aspirational or invented. Use when asked to "docs drift", "sync docs with code", "audit documentation", "stale README", "onboarding docs broken", "doc sync plan", "phantom docs", or "docs out of date".
kensaurus/cursor-kenji/skills/plan-error-handling Skill
8★ repoAudit a codebase for silent failures, swallowed exceptions, and observability gaps across Sentry and Langfuse, then produce a phased fix plan. Use when the user says "errors aren't showing in Sentry", "things fail silently", "empty catch blocks", "add error handling", "check my Langfuse tracing", or is hardening observability before launch. Covers error handling and LLM observability (untraced model calls, missing cost/latency, no eval scores). Plan only until each phase is approved. Pairs with backend-observability, debug-sentry-monitor, audit-langfuse-llm. Do NOT use for live incidents (debug-error).
kensaurus/cursor-kenji/skills/plan-input-validation Skill
8★ repoAudit every trust boundary for unvalidated input, injection, and forged-request gaps, then produce a phased hardening plan. Use when the user says "validate my inputs", "is my app injection-safe", "check my forms", "XSS", "dangerouslySetInnerHTML", "my Stripe webhook", "can someone forge requests", or is hardening before launch. AI code has happy-path bias: missing Zod, dangerouslySetInnerHTML without DOMPurify, webhook signature gaps (empty or unchecked signing secrets), raw-body signature mistakes, missing idempotency. Stack-aware for Supabase, Stripe, Next.js. Plan only until each phase is approved. Pairs with plan-rls-audit, plan-security-audit, audit-fe-api. Do NOT use for row access (plan-rls-audit) or secrets (plan-secrets-audit).
kensaurus/cursor-kenji/skills/plan-llm-cost-guardrails Skill
8★ repoAudit an LLM-powered app for runaway-cost and quota-abuse exposure, then produce a phased guardrail plan. Use when the user says "cap my AI costs", "my LLM bill could blow up", "rate limit my AI", "token budget", "runaway agent loop", or is hardening LLM features before launch. Audits three layers: token-bucket limits, cost-velocity circuit breakers, and fallback chains; also covers Langfuse cost alerts and streaming usage accounting. Plan only until approved. Pairs with audit-langfuse-llm, plan-input-validation. Do NOT use for output quality evals (audit-langfuse-llm).
kensaurus/cursor-kenji/skills/plan-mobile-readiness Skill
8★ repoAudit a Capacitor/React Native app for App Store and Google Play submission readiness, then produce a phased pre-submission plan. Use when the user says "is my app ready for the App Store", "will Google Play reject this", "pre-submission check", "privacy manifest", "data safety form", or is preparing a mobile launch. Audits PrivacyInfo.xcprivacy, permission/Data-Safety match, IAP via store billing, target API level, demo creds, and placeholder UI. Plan only until approved. Pairs with mobile-capacitor-platform, enhance-capacitor-ui, plan-stub-checker. Do NOT use for perf tuning or screen polish.
kensaurus/cursor-kenji/skills/plan-perf-audit Skill
8★ repoMeasure-don't-guess performance audit across web, mobile, backend, and data layers — produces burndown and optimization plan with no fixes in this pass. No fabricated metrics; every issue needs a measured baseline or [NEEDS PROFILING]. Research-backed proposals for React (code-split, memo, react-window, startTransition), RN (Hermes, JSI, <2s cold start), data N+1/index work with EXPLAIN, and prevention via Lighthouse CI budgets + RUM. Mobile thresholds stricter than web CWV. Use when asked to "performance audit plan", "perf burndown", "measure before optimize", "bundle size audit", "LCP slow", "N+1 audit plan", "plan performance improvements", or "Core Web Vitals audit".
kensaurus/cursor-kenji/skills/plan-rls-audit Skill
8★ repoAudit a Supabase/Postgres project for Row-Level Security and access-control gaps, then produce a phased remediation plan. Use when the user says "RLS", "is my Supabase secure", "anyone can read my data", "lock down my tables", "service_role key", or is hardening before launch. Audits every table for relrowsecurity, permissive/inverted policies, client-side service_role keys, and auth.uid() correctness. Plan only — nothing altered until approved. Pairs with plan-secrets-audit, plan-security-audit, audit-db-schema. Do NOT use for query performance (backend-db-performance) or non-Postgres backends.
kensaurus/cursor-kenji/skills/plan-secrets-audit Skill
8★ repoAudit a codebase and git history for exposed credentials and mis-scoped keys, then produce a phased rotation-and-remediation plan. Use when the user says "check for hardcoded secrets", "are my API keys exposed", "did I commit a key", "secret scan", "is my .env safe", "rotate keys", or is hardening before launch or open-sourcing. Vibe-coded apps ship keys in client bundles; secrets committed once live in git history forever — ROTATE, not just relocate. Scans sk_/pk_/whsec_/service_role, separates safe-client (anon, publishable) from never-client (service_role, secret), flags history needing rotation, checks NEXT_PUBLIC_ exposure and Vercel/AWS env config. Plan only until approved. Pairs with plan-rls-audit. Do NOT use for RLS logic or input validation.
kensaurus/cursor-kenji/skills/plan-security-audit Skill
8★ repoOWASP Top 10 security audit with Supabase-first methodology — RLS pass, bundle/secret scan, auth-path tracing, dependency CVEs. Plan only, no patches or destructive testing. Never paste secret values — location + rotation flag only. Research-backed: tables without RLS and service_role in client bundle as top critical classes. Use when asked to "security audit plan", "OWASP audit", "RLS audit", "Supabase security review", "hardening plan", "secrets scan plan", "plan security fixes", or "security burndown".
kensaurus/cursor-kenji/skills/plan-stub-checker Skill
8★ repoExhaustive audit for stubs, dead buttons, fake/placeholder components, unwired handlers, dead links, orphans, and severed integrations — produces a burndown and wiring plan with no implementation in this pass. Traces intended backend, Supabase, Sentry, and data-pipeline targets; conservative false-positive filtering. Plan only — user approves before wiring. Uses codebase static analysis + optional Playwright/Sentry/Supabase MCP. Use when asked to "find dead buttons", "stub checker", "fake components", "unwired handlers", "dead links", "orphaned components", "plan stub wiring", "what's not connected", "mock data in prod", "buttons that do nothing", or "stub audit".
kensaurus/cursor-kenji/skills/plan-test-coverage Skill
8★ repoUser-story-driven test coverage audit and plan — no test writing in this pass. Derives stories from real code, builds story-to-test traceability matrix, detects fake-green and weak tests, multi-lens coverage (branch/path/risk/integration/mutation). Coverage numbers from real runs or [NEEDS RUN]. Natural lock-in after stub-wiring. Use when asked to "test coverage plan", "coverage audit", "traceability matrix", "fake-green tests", "uncovered user stories", "plan tests for critical flows", "mutation testing plan", or "what's not tested".
kensaurus/cursor-kenji/skills/plan-uiux-unification Skill
8★ repoExhaustive, non-destructive UI/UX and design-system audit that produces a burndown and unification plan — no code changes until each phase is approved. Covers IA hierarchy, surface inventory, per-surface violation log, prioritized burndown with risk column, and phased enhancement roadmap. Enhances the existing design system; does not replace it. Use when asked to "audit UI without fixing", "UI burndown", "unify the design system", "design system consolidation", "IA audit before redesign", or "UI/UX unification plan". Pairs with audit-uiux-design-system. Do NOT use for live UI fixes (audit-uiux-design-system).
kensaurus/cursor-kenji/skills/workflow-spec-tdd Skill
8★ repoStop vibe-coding with a spec → plan → TDD loop before writing a line. Use for any non-trivial feature, refactor, or bug fix on web, React Native, or Capacitor. Use when asked to "build", "implement", "add a feature", "this keeps breaking", "do it properly", or when LLM output keeps being wrong.
ericluo04/claude-academic-workflow/skills/preregister Skill
no license8★ repoDraft a registry-ready preregistration or preanalysis plan (AsPredicted, OSF, or AEA RCT Registry) from a study spec or a free-form description, with MUST/SHOULD/MAY flags on every field, [CLARIFY:] placeholders instead of invented content, a stated target N with power basis and stopping rule, and an explicit falsification criterion. TRIGGER on "preregister", "draft a preregistration", "AsPredicted form", "OSF prereg", "AEA RCT registry", "PAP", "preanalysis plan", or before launching a vignette, conjoint, eye-tracking, MTurk/Prolific, or field experiment. Refuses to write a preregistration for analyses already run on data already seen. Writes Markdown for pasting into the web forms, .tex on request.
rampstackco/claude-skills-seo/skills/seo-keyword Skill
8★ repoRun keyword research, classify by search intent, cluster into topical groups, and prioritize for content production. Use this skill whenever the user asks to do keyword research, find target keywords, identify ranking opportunities, classify search intent, build a topical map, or plan a content strategy around what people search for. Triggers on keyword research, keyword strategy, search intent, keyword clustering, topic clusters, keyword difficulty, search volume, ranking opportunity, content gap, what should I write about, target keyword, primary keyword, secondary keyword, long-tail. Also triggers when planning a content calendar or new site without keywords yet defined.
The same file is in 4 other repositories
sumitaich1998/jarvisvr/skills/orchestration/task-decomposition Skill
8★ repoBreak a user's goal into a small DAG of sub-tasks for the JarvisVR specialist team, then emit it as an orchestration.plan. Use whenever a request needs more than one capability or agent, e.g. "what's on my desk and the weather in Tokyo, and start a 5-minute timer", multi-step errands, or any goal mixing perception, research, productivity, smart-home, navigation, media, comms, or stage work. Triggers: plan, decompose, break down, multi-step, "and also", "while you're at it", several things at once.
jpoindexter/nd-skills/skills/nd-task-decomposition Skill
8★ repoDiagnosis-free neurodivergent support skills for AI coding agents, with executive-function scaffolds and always-on Claude/Codex behaviors.
Dragoon0x/taste-skills/skills/judgment/taste-as-strategy Skill
8★ repoUse taste as a competitive moat and business advantage. In the AI and vibe-coding era, execution is commoditized. Taste is the defensible edge. Use when advising founders on product differentiation, building product culture, evaluating why some products win despite fewer features, or understanding taste as a strategic asset.
matematicsolutions/awesome-matematic-skills-pl/dev-mcp/skills/matematic-spec-driven Skill
8★ repoPolish hub of legal-AI skills - 41 skills in 8 Claude Code / Cowork bundles (LLM output verification, PL/EU case law, DOCX redline, AI Act audit bundle). GDPR-safe, vendor-neutral, MIT.
matematicsolutions/awesome-matematic-skills-pl/governance-kancelarii/skills/matematic-konstytucja-ai Skill
8★ repoPolish hub of legal-AI skills - 41 skills in 8 Claude Code / Cowork bundles (LLM output verification, PL/EU case law, DOCX redline, AI Act audit bundle). GDPR-safe, vendor-neutral, MIT.
stark-ai-de/agent-skills/incubator/skills/engineering-workflows/issue-plan-slicer Skill
8★ repoConvert a spec, roadmap item, or rough plan into independently implementable issue slices with scope, dependencies, acceptance criteria, and validation. Use when the user asks to split work into GitHub issues, local markdown tasks, or agent-ready implementation chunks.
stark-ai-de/agent-skills/incubator/skills/engineering-workflows/prd-writer Skill
8★ repoWrite a concise PRD or implementation brief from current context, separating problem, solution, user stories, decisions, testing, rollout, and out of scope. Use when the user asks for a PRD, product brief, implementation brief, or spec handoff.
stark-ai-de/agent-skills/incubator/skills/productivity/grill-plan Skill
8★ repoRelentlessly question a plan, design, migration, release, or repo maintenance proposal until assumptions, risks, constraints, and decision branches are clear. Use when the user wants to be grilled before implementation or wants a plan challenged.
stark-ai-de/agent-skills/skills/claude-operations/claude-spec-interviewer Skill
8★ repoInterview fuzzy Claude Code coding requests into user-verified implementation specs with source challenge, ADR gate, validation plan, and execution prompt. Use when the user asks for /claude-spec-interviewer, a Claude Code implementation plan, PRD, requirements, plan before coding, Plan Mode planning, persisted spec, ADR decision, CLAUDE.md evidence, or .claude/rules evidence. Do not use for direct implementation, pure brainstorming, memory cleanup, or authoring Claude instruction files only.
stark-ai-de/agent-skills/skills/codex-operations/codex-spec-interviewer Skill
8★ repoInterview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
stark-ai-de/agent-skills/skills/cursor-operations/cursor-spec-interviewer Skill
8★ repoInterview fuzzy Cursor Agent coding requests into user-verified, Cursor-ready implementation specs. Use when the user asks for a spec, implementation plan, PRD, requirements, or a plan before coding for a feature, bugfix, refactor, migration, repo-wide change, or architecture task, or needs acceptance criteria, validation commands, ADR decisions, or rollout notes. Saves the spec and a Cursor execution prompt. Do not use for fully specified tasks or direct implementation requests.
quivly/skills/customer-engineering/churn-save-plan Skill
8★ repoDeep-dives a red account and produces a structured save plan — root causes ranked, save plays matched to causes, and a realistic assessment of whether the account is savable. Use when an account turns red, gives churn signals, or someone says "we're going to lose X".
quivly/skills/customer-engineering/escalation-brief Skill
8★ repoBuilds an executive escalation one-pager — issue timeline, business impact, customer temperature, and specific asks. Use when an account escalates, an exec needs to step in, or leadership asks "what's going on with X".
quivly/skills/customer-engineering/expansion-scan Skill
8★ repoScans an account or a whole book for expansion signals — usage nearing plan limits, new teams appearing, whitespace against products owned, and buying signals in conversations. Use for expansion planning, pipeline generation from the install base, or "where's the upsell in my book".
hamzabellouch/agent-skills/Google Workspace Automation/gws-recipe-create-task-list Skill
8★ repoSet up a new Google Tasks list with initial tasks.
The same file is in 2 other repositories
Gws recipe plan weekly schedule
hamzabellouch/agent-skills/Google Workspace Automation/gws-recipe-plan-weekly-schedule Skill
8★ repoReview your Google Calendar week, identify gaps, and add events to fill them.
The same file is in 2 other repositories
hamzabellouch/agent-skills/Marketing and Growth/marketing-ad-creative Skill
8★ repoWhen the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' 'static ads,' 'static ad concepts,' 'ad templates,' 'iMessage ad,' 'chat reveal ad,' 'fake DM ad,' 'ChatGPT ad,' 'Apple Notes ad,' 'AirDrop ad,' 'creative strategy,' 'creative roadmap,' 'creative retro,' 'hook writing,' 'creative review page,' 'present ad creative for approval,' 'motion video ad,' 'faceless video ad,' 'animated explainer ad,' 'motion collage ad,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.
The same file is in 2 other repositories
hamzabellouch/agent-skills/Marketing and Growth/marketing-content-strategy Skill
8★ repoWhen the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.
The same file is in 5 other repositories
hamzabellouch/agent-skills/Marketing and Growth/marketing-lead-magnets Skill
8★ repoWhen the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the user mentions "lead magnet," "gated content," "content upgrade," "downloadable," "ebook," "cheat sheet," "checklist," "template download," "opt-in," "freebie," "PDF download," "resource library," "content offer," "email capture content," "Notion template," "spreadsheet template," or "what should I give away for emails." Use this for planning what to create and how to distribute it. For interactive tools as lead magnets, see free-tools. For writing the actual content, see copywriting. For the email sequence after capture, see emails.
The same file is in 5 other repositories
hamzabellouch/agent-skills/Marketing and Growth/marketing-marketing-plan Skill
8★ repoWhen the user needs a comprehensive marketing plan for a client, a company they advise, or their own product. Also use when the user mentions "marketing plan," "growth plan," "GTM plan," "go-to-market plan," "AARRR plan," "90-day marketing plan," "12-month marketing roadmap," "fractional CMO plan," or "fCMO plan." Generates an exhaustive 13-section plan structured by AARRR (Acquisition, Activation, Retention, Referral, Revenue), customized to the client's current budget, team, and stage, mapped to future funding milestones, cross-referenced with the 139-idea marketing-ideas library and an embedded 17-section current-state audit rubric, with a full marketing operations stack showing which skills and MCP/API integrations execute each part. Outputs a Notion-paste-ready markdown document. For positioning and ICP context before planning, see product-marketing. For stage-specific deep work, see onboarding, signup, emails, referrals, pricing.
The same file is in 3 other repositories
hamzabellouch/agent-skills/Marketing and Growth/marketing-site-architecture Skill
8★ repoWhen the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.
The same file is in 5 other repositories