Results for “growth-log”

Expert in designing and optimizing growth loops - self-reinforcing systems where the output of one cycle becomes the input for the next. Covers viral loops, content loops, paid loops, sales loops, and product loops. Knows how to identify, measure, and accelerate the specific loop mechanics that drive sustainable growth. Use when "growth loop, viral loop, content loop, flywheel, compounding growth, acquisition loop, referral loop, " mentioned.

Identifies and designs growth loops (flywheels) for sustainable traction — evaluating 5 loop types: Viral, Usage, Collaboration, User-Generated, and Referral. Use when designing growth mechanisms or reducing reliance on paid acquisition. Triggers on: growth loop, flywheel, viral loop, referral program, product-led growth, PLG, user acquisition, growth strategy, retention loop, compounding growth.

Drive systematic growth with acquisition loops, experimentation frameworks, retention systems, and product-led strategies.

Growth strategy for product-led and loop-driven growth systems. Use when building growth strategy, designing growth loops, planning acquisition channels, evaluating network effects, deciding when to scale, or coordinating product, engineering, data, and marketing around growth. For SEO audits use seo-and-aeo-strategy; for page/form CRO use conversion-rate-optimization; for A/B test design use ab-test-setup.

Design product-led growth strategies with self-serve funnels and expansion revenue. TRIGGERS - Use when user needs help with plg-strategy related tasks.

Identify growth loops (flywheels) for sustainable traction. Evaluates 5 loop types: Viral, Usage, Collaboration, User-Generated, and Referral. Use when designing growth mechanisms, building product-led traction, or understanding how growth loops work.

Build self-serve acquisition and expansion motions, including deciding between PLG and sales-led, optimizing activation, driving freemium conversion, and building growth equations.

Design product-led growth loops, activation paths, and expansion mechanics for a software product. Use when the team needs onboarding-to-value planning, sharing or collaboration loops, retention hooks, or realistic post-launch growth motions tied to product usage.

Identify and design growth loops (flywheels) for sustainable traction, evaluating five proven mechanisms: viral, usage, collaboration, user-generated, and referral.

Log workouts, plan routines, track progress, and get intelligent coaching for any fitness level.

Build and debug Retrieval-Augmented Generation pipelines — chunking, embedding, retrieval, reranking

Designs growth experiments, tests acquisition channels, builds viral loops, and analyzes metrics to optimize conversion funnels.

Use this skill for growth funnels, landing pages, analytics, experiments, activation and conversion. Trigger when the task involves agent profile work related to Growth Engineer Agent, implementation, audits, debugging, strategy, or validation.

Launch community-powered growth campaigns across social platforms: amplify posts with authentic engagement (replies, likes, reposts) and discover relevant conversations to join.

Standards for structured logging and observability in Golang. Use when adding structured logging or tracing to Go services.

Generates and maintains CHANGELOG.md files following Keep a Changelog conventions — from git history, commit messages, or a description of changes. Use when asked to write a changelog, update release notes, or document what changed in a version.

Runs a closed-loop SEO growth workflow using Search Console data, keyword demand analysis, SERP Authority Mark checks, and the available publishing path, adapting to CMS/API, local repo, hybrid, and advisory-only environments.

Generates a comprehensive narrative report analyzing a project's entire development history from claude-mem's persistent memory timeline.

Creates or updates CHANGELOG.md following the Keep a Changelog 1.1.0 format. Use this skill when the user asks to "update the changelog", "generate changelog", "add changelog entry", "create CHANGELOG.md", "sync changelog with tags", or wants to document project changes based on git tags and commit history.

debug-logging

Community-powered growth for builders. Boost amplifies your social posts with authentic community engagement (replies, likes, reposts). Discover finds relevant conversations and generates AI-powered replies at scale. Use Boost when the user has a post URL. Use Discover when the user wants to find and engage in conversations about their product.

Design product-led growth strategies with self-serve funnels and expansion revenue. TRIGGERS - Use when user needs help with plg-strategy related tasks.

Analyzes git commit history and generates structured changelogs categorized by change type.

Guides agents through the full lifecycle of NeMo-RL experiments: understanding recipes, launching reproducible runs, analyzing results, and preserving human oversight with git and TSV logs.

Generate changelogs from git history and validate conventional commits. Usage: /changelog <generate|lint> [options]

Expert en croissance virale (K-factor, network effects, referral loops, embedded virality)

Records daily activities, progress, decisions, and learnings in structured chronological markdown files.

Runs a data augmentation pipeline on a given input and reports pass/fail per transform, diagnosing failures against known issues.

Logs board meeting decisions with a two-layer memory architecture, separating raw transcripts from approved decisions, and provides commands to review past decisions and overdue action items.

Analyzes recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and sends a personalized growth report to Slack DMs.

当需要建立结构化的每日例行程序，以支持不同阶段的个人成长目标时

Use to find where support can drive adoption, referral and retention without turning into a sales channel, and to measure whether it worked. Trigger for "can support drive growth", "support-led growth programme", "should agents mention other features", advocacy and referral from support, adoption nudges in support conversations, or a support team being given a revenue target.

Investigate a problem, log it to the debug changelog, cross-check past issues, and suggest a non-duplicate fix.

Audits a project's developer experience by scoring devcontainer, git hooks, linting, build caching, environment setup, and release pipeline, then generates a DX health report with prioritized recommendations.