novahiz 0.2.2 → 0.2.5

package/bundled-skills/eas-workflows/SKILL.md

@@ -1,99 +0,0 @@
----
-name: eas-workflows
-description: EAS service (paid). Helps understand and write EAS workflow YAML files for Expo projects. Use this skill when the user asks about CI/CD or workflows in an Expo or EAS context, mentions .eas/workflows/, or wants help with EAS build pipelines or deployment automation.
-allowed-tools: "Read,Write,Bash(node:*),Bash(npx *eas-cli@*)"
-version: 1.0.0
-license: MIT License
----
-
-# EAS Workflows Skill
-
-> **EAS service - costs apply.** EAS Workflows run on Expo Application Services, a paid product with free-tier limits. Each workflow job consumes your plan's build/compute minutes, and jobs that build or submit also need paid Apple Developer and Google Play accounts. Review https://expo.dev/pricing before triggering runs.
-
-Help developers write and edit EAS CI/CD workflow YAML files.
-
-## Reference Documentation
-
-Fetch these resources before generating or editing workflow files, or when answering syntax questions. First resolve this skill's directory, then use the fetch script in its `scripts/` directory. It is implemented using Node.js and caches responses using ETags for efficiency:
-
-```bash
-# Fetch resources
-node <skill-dir>/scripts/fetch.js <url>
-```
-
-1. **JSON Schema** — https://api.expo.dev/v2/workflows/schema
-   - It is NECESSARY to fetch this schema
-   - Source of truth for the workflow YAML structure; EAS CLI remains the authoritative final validator
-   - All job types and their required/optional parameters
-   - Trigger types and configurations
-   - Runner types, VM images, and all enums
-
-2. **Syntax Documentation** — https://raw.githubusercontent.com/expo/expo/refs/heads/main/docs/pages/eas/workflows/syntax.mdx
-   - Overview of workflow YAML syntax
-   - Examples and English explanations
-   - Expression syntax and contexts
-
-3. **Pre-packaged Jobs** — https://raw.githubusercontent.com/expo/expo/refs/heads/main/docs/pages/eas/workflows/pre-packaged-jobs.mdx
-   - Documentation for supported pre-packaged job types
-   - Job-specific parameters and outputs
-
-Do not rely on memorized values; these resources evolve as new features are added.
-
-## Workflow File Location
-
-Workflows live in `.eas/workflows/*.yml` (or `.yaml`). Each file must be 16 KiB or smaller.
-
-## Top-Level Structure
-
-A workflow file has these top-level keys:
-
-- `name` — Display name for the workflow
-- `on` — Triggers that start the workflow (at least one required)
-- `jobs` — Job definitions (required)
-- `defaults` — Shared defaults for all jobs
-- `concurrency` — Control parallel workflow runs
-
-Consult the schema for the full specification of each section.
-
-## Expressions
-
-Use `${{ }}` syntax for dynamic values. The schema defines available contexts:
-
-- `github.*` — GitHub repository and event information
-- `inputs.*` — Values from `workflow_dispatch` inputs
-- `needs.*` — Outputs and status from dependent jobs
-- `jobs.*` — Job outputs (alternative syntax)
-- `steps.*` — Step outputs within custom jobs
-- `workflow.*` — Workflow metadata
-
-## Generating Workflows
-
-When generating or editing workflows:
-
-1. Fetch the schema to get current job types, parameters, and allowed values
-2. Validate that required fields are present for each job type
-3. Verify job references in `needs` and `after` exist in the workflow
-4. Check that expressions reference valid contexts and outputs
-5. Ensure `if` conditions respect the schema's length constraints
-
-## Validation
-
-After generating or editing a workflow file, validate it with EAS CLI from the Expo project root:
-
-```sh
-npx -y eas-cli@latest workflow:validate .eas/workflows/<workflow.yml> --non-interactive
-```
-
-Run the command separately for each changed workflow file. It requires a logged-in EAS CLI session and a linked Expo project. Unlike schema-only validation, it also checks build profile references against the project's `eas.json` and performs EAS server-side validation. Fix every reported error and rerun the command until it prints `Workflow configuration YAML is valid.` Do not replace this command with a local YAML or JSON Schema validator.
-
-## Answering Questions
-
-When users ask about available options (job types, triggers, runner types, etc.), fetch the schema and derive the answer from it rather than relying on potentially outdated information.
-
-## Submitting Feedback
-If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
-```bash
-npx --yes submit-expo-feedback@latest --category skills --subject "eas-workflows" "<actionable feedback>"
-```
-Only submit when you have something specific and actionable to report. Include as much relevant context as possible.
-If an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.

package/bundled-skills/eas-workflows/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "EAS Workflows"
-  short_description: "Paid EAS service. Write and validate EAS workflow YAML files for Expo projects"
-  default_prompt: "Use $eas-workflows when creating or editing .eas/workflows YAML, validating EAS workflow configuration, or answering questions about workflow triggers, jobs, runners, and expressions."

package/bundled-skills/eas-workflows/scripts/fetch.js

@@ -1,109 +0,0 @@
-#!/usr/bin/env node
-
-import { createHash } from 'node:crypto';
-import { readFile, writeFile, mkdir } from 'node:fs/promises';
-import { resolve } from 'node:path';
-import process from 'node:process';
-
-const CACHE_DIRECTORY = resolve(import.meta.dirname, '.cache');
-const DEFAULT_TTL_SECONDS = 15 * 60; // 15 minutes
-
-export async function fetchCached(url) {
-  await mkdir(CACHE_DIRECTORY, { recursive: true });
-
-  const cacheFile = resolve(CACHE_DIRECTORY, hashUrl(url) + '.json');
-  const cached = await loadCacheEntry(cacheFile);
-  if (cached && cached.expires > Math.floor(Date.now() / 1000)) {
-    return cached.data;
-  }
-
-  // Make request, with conditional If-None-Match if we have an ETag.
-  // Cache-Control: max-age=0 overrides Node's default 'no-cache' to allow 304 responses.
-  const response = await fetch(url, {
-    headers: {
-      'Cache-Control': 'max-age=0',
-      ...(cached?.etag && { 'If-None-Match': cached.etag }),
-    },
-  });
-
-  if (response.status === 304 && cached) {
-    // Refresh expiration and return cached data
-    const entry = { ...cached, expires: getExpires(response.headers) };
-    await saveCacheEntry(cacheFile, entry);
-    return cached.data;
-  }
-
-  if (!response.ok) {
-    throw new Error(`HTTP ${response.status}: ${response.statusText}`);
-  }
-
-  const etag = response.headers.get('etag');
-  const data = await response.text();
-  const expires = getExpires(response.headers);
-
-  await saveCacheEntry(cacheFile, { url, etag, expires, data });
-
-  return data;
-}
-
-function hashUrl(url) {
-  return createHash('sha256').update(url).digest('hex').slice(0, 16);
-}
-
-async function loadCacheEntry(cacheFile) {
-  try {
-    return JSON.parse(await readFile(cacheFile, 'utf-8'));
-  } catch {
-    return null;
-  }
-}
-
-async function saveCacheEntry(cacheFile, entry) {
-  await writeFile(cacheFile, JSON.stringify(entry, null, 2));
-}
-
-function getExpires(headers) {
-  const now = Math.floor(Date.now() / 1000);
-
-  // Prefer Cache-Control: max-age
-  const maxAgeSeconds = parseMaxAge(headers.get('cache-control'));
-  if (maxAgeSeconds != null) {
-    return now + maxAgeSeconds;
-  }
-
-  // Fall back to Expires header
-  const expires = headers.get('expires');
-  if (expires) {
-    const expiresTime = Date.parse(expires);
-    if (!Number.isNaN(expiresTime)) {
-      return Math.floor(expiresTime / 1000);
-    }
-  }
-
-  // Default TTL
-  return now + DEFAULT_TTL_SECONDS;
-}
-
-function parseMaxAge(cacheControl) {
-  if (!cacheControl) {
-    return null;
-  }
-  const match = cacheControl.match(/max-age=(\d+)/i);
-  return match ? parseInt(match[1], 10) : null;
-}
-
-if (import.meta.main) {
-  const url = process.argv[2];
-
-  if (!url || url === '--help' || url === '-h') {
-    console.log(`Usage: fetch <url>
-
-Fetches a URL with HTTP caching (ETags + Cache-Control/Expires).
-Default TTL: ${DEFAULT_TTL_SECONDS / 60} minutes.
-Cache is stored in: ${CACHE_DIRECTORY}/`);
-    process.exit(url ? 0 : 1);
-  }
-
-  const data = await fetchCached(url);
-  console.log(data);
-}

package/bundled-skills/eas-workflows/scripts/package.json

@@ -1,6 +0,0 @@
-{
-  "name": "@expo/eas-workflows-skill",
-  "version": "0.0.0",
-  "private": true,
-  "type": "module"
-}

package/bundled-skills/emails/SKILL.md

@@ -1,311 +0,0 @@
----
-name: emails
-description: When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.
-metadata:
-  version: 2.0.0
----
-
-# Email Sequence Design
-
-You are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion.
-
-## Initial Assessment
-
-**Check for product marketing context first:**
-If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
-
-Before creating a sequence, understand:
-
-1. **Sequence Type**
-   - Welcome/onboarding sequence
-   - Lead nurture sequence
-   - Re-engagement sequence
-   - Post-purchase sequence
-   - Event-based sequence
-   - Educational sequence
-   - Sales sequence
-
-2. **Audience Context**
-   - Who are they?
-   - What triggered them into this sequence?
-   - What do they already know/believe?
-   - What's their current relationship with you?
-
-3. **Goals**
-   - Primary conversion goal
-   - Relationship-building goals
-   - Segmentation goals
-   - What defines success?
-
----
-
-## Core Principles
-
-### 1. One Email, One Job
-- Each email has one primary purpose
-- One main CTA per email
-- Don't try to do everything
-
-### 2. Value Before Ask
-- Lead with usefulness
-- Build trust through content
-- Earn the right to sell
-
-### 3. Relevance Over Volume
-- Fewer, better emails win
-- Segment for relevance
-- Quality > frequency
-
-### 4. Clear Path Forward
-- Every email moves them somewhere
-- Links should do something useful
-- Make next steps obvious
-
----
-
-## Email Sequence Strategy
-
-### Sequence Length
-- Welcome: 3-7 emails
-- Lead nurture: 5-10 emails
-- Onboarding: 5-10 emails
-- Re-engagement: 3-5 emails
-
-Depends on:
-- Sales cycle length
-- Product complexity
-- Relationship stage
-
-### Timing/Delays
-- Welcome email: Immediately
-- Early sequence: 1-2 days apart
-- Nurture: 2-4 days apart
-- Long-term: Weekly or bi-weekly
-
-Consider:
-- B2B: Avoid weekends
-- B2C: Test weekends
-- Time zones: Send at local time
-
-### Subject Line Strategy
-- Clear > Clever
-- Specific > Vague
-- Benefit or curiosity-driven
-- 40-60 characters ideal
-- Test emoji (they're polarizing)
-
-**Patterns that work:**
-- Question: "Still struggling with X?"
-- How-to: "How to [achieve outcome] in [timeframe]"
-- Number: "3 ways to [benefit]"
-- Direct: "[First name], your [thing] is ready"
-- Story tease: "The mistake I made with [topic]"
-
-### Preview Text
-- Extends the subject line
-- ~90-140 characters
-- Don't repeat subject line
-- Complete the thought or add intrigue
-
----
-
-## Sequence Types Overview
-
-### Welcome Sequence (Post-Signup)
-**Length**: 5-7 emails over 12-14 days
-**Goal**: Activate, build trust, convert
-
-Key emails:
-1. Welcome + deliver promised value (immediate)
-2. Quick win (day 1-2)
-3. Story/Why (day 3-4)
-4. Social proof (day 5-6)
-5. Overcome objection (day 7-8)
-6. Core feature highlight (day 9-11)
-7. Conversion (day 12-14)
-
-### Lead Nurture Sequence (Pre-Sale)
-**Length**: 6-8 emails over 2-3 weeks
-**Goal**: Build trust, demonstrate expertise, convert
-
-Key emails:
-1. Deliver lead magnet + intro (immediate)
-2. Expand on topic (day 2-3)
-3. Problem deep-dive (day 4-5)
-4. Solution framework (day 6-8)
-5. Case study (day 9-11)
-6. Differentiation (day 12-14)
-7. Objection handler (day 15-18)
-8. Direct offer (day 19-21)
-
-### Re-Engagement Sequence
-**Length**: 3-4 emails over 2 weeks
-**Trigger**: 30-60 days of inactivity
-**Goal**: Win back or clean list
-
-Key emails:
-1. Check-in (genuine concern)
-2. Value reminder (what's new)
-3. Incentive (special offer)
-4. Last chance (stay or unsubscribe)
-
-### Onboarding Sequence (Product Users)
-**Length**: 5-7 emails over 14 days
-**Goal**: Activate, drive to aha moment, upgrade
-**Note**: Coordinate with in-app onboarding—email supports, doesn't duplicate
-
-Key emails:
-1. Welcome + first step (immediate)
-2. Getting started help (day 1)
-3. Feature highlight (day 2-3)
-4. Success story (day 4-5)
-5. Check-in (day 7)
-6. Advanced tip (day 10-12)
-7. Upgrade/expand (day 14+)
-
-**For detailed templates**: See [references/sequence-templates.md](references/sequence-templates.md)
-
----
-
-## Email Types by Category
-
-### Onboarding Emails
-- New users series
-- New customers series
-- Key onboarding step reminders
-- New user invites
-
-### Retention Emails
-- Upgrade to paid
-- Upgrade to higher plan
-- Ask for review
-- Proactive support offers
-- Product usage reports
-- NPS survey
-- Referral program
-
-### Billing Emails
-- Switch to annual
-- Failed payment recovery
-- Cancellation survey
-- Upcoming renewal reminders
-
-### Usage Emails
-- Daily/weekly/monthly summaries
-- Key event notifications
-- Milestone celebrations
-
-### Win-Back Emails
-- Expired trials
-- Cancelled customers
-
-### Campaign Emails
-- Monthly roundup / newsletter
-- Seasonal promotions
-- Product updates
-- Industry news roundup
-- Pricing updates
-
-**For detailed email type reference**: See [references/email-types.md](references/email-types.md)
-
----
-
-## Email Copy Guidelines
-
-### Structure
-1. **Hook**: First line grabs attention
-2. **Context**: Why this matters to them
-3. **Value**: The useful content
-4. **CTA**: What to do next
-5. **Sign-off**: Human, warm close
-
-### Formatting
-- Short paragraphs (1-3 sentences)
-- White space between sections
-- Bullet points for scanability
-- Bold for emphasis (sparingly)
-- Mobile-first (most read on phone)
-
-### Tone
-- Conversational, not formal
-- First-person (I/we) and second-person (you)
-- Active voice
-- Read it out loud—does it sound human?
-
-### Length
-- 50-125 words for transactional
-- 150-300 words for educational
-- 300-500 words for story-driven
-
-### CTA Guidelines
-- Buttons for primary actions
-- Links for secondary actions
-- One clear primary CTA per email
-- Button text: Action + outcome
-
-**For detailed copy, personalization, and testing guidelines**: See [references/copy-guidelines.md](references/copy-guidelines.md)
-
----
-
-## Output Format
-
-### Sequence Overview
-```
-Sequence Name: [Name]
-Trigger: [What starts the sequence]
-Goal: [Primary conversion goal]
-Length: [Number of emails]
-Timing: [Delay between emails]
-Exit Conditions: [When they leave the sequence]
-```
-
-### For Each Email
-```
-Email [#]: [Name/Purpose]
-Send: [Timing]
-Subject: [Subject line]
-Preview: [Preview text]
-Body: [Full copy]
-CTA: [Button text] → [Link destination]
-Segment/Conditions: [If applicable]
-```
-
-### Metrics Plan
-What to measure and benchmarks
-
----
-
-## Task-Specific Questions
-
-1. What triggers entry to this sequence?
-2. What's the primary goal/conversion action?
-3. What do they already know about you?
-4. What other emails are they receiving?
-5. What's your current email performance?
-
----
-
-## Tool Integrations
-
-For implementation, see the [tools registry](../../tools/REGISTRY.md). Key email tools:
-
-| Tool | Best For | MCP | Guide |
-|------|----------|:---:|-------|
-| **Customer.io** | Behavior-based automation | - | [customer-io.md](../../tools/integrations/customer-io.md) |
-| **Mailchimp** | SMB email marketing | ✓ | [mailchimp.md](../../tools/integrations/mailchimp.md) |
-| **Nitrosend** | AI-native email (sequences via prompts) | ✓ | [nitrosend.md](../../tools/integrations/nitrosend.md) |
-| **Resend** | Developer-friendly transactional | ✓ | [resend.md](../../tools/integrations/resend.md) |
-| **SendGrid** | Transactional email at scale | - | [sendgrid.md](../../tools/integrations/sendgrid.md) |
-| **Kit** | Creator/newsletter focused | - | [kit.md](../../tools/integrations/kit.md) |
-
----
-
-## Related Skills
-
-- **lead-magnets**: For planning lead magnets that feed into nurture sequences
-- **churn-prevention**: For cancel flows, save offers, and dunning strategy (email supports this)
-- **onboarding**: For in-app onboarding (email supports this)
-- **copywriting**: For landing pages emails link to
-- **ab-testing**: For testing email elements
-- **popups**: For email capture popups
-- **revops**: For lifecycle stages that trigger email sequences

package/bundled-skills/emails/evals/evals.json

@@ -1,93 +0,0 @@
-{
-  "skill_name": "emails",
-  "evals": [
-    {
-      "id": 1,
-      "prompt": "Create a welcome email sequence for new users who sign up for our project management tool's free trial. The trial is 14 days. We want to get them to their aha moment (creating their first project and inviting a team member).",
-      "expected_output": "Should check for product-marketing.md first. Should create a welcome sequence (5-7 emails) following the core principles: one email one job, value before ask. Should map each email to a specific goal in the 14-day trial journey. Should include timing/delays between emails. Each email should follow the email copy structure: hook → context → value → CTA → sign-off. Should include subject lines following the subject line strategy. Should align sequence with the aha moment (first project + team invite). Output should follow the structured format with sequence overview and per-email specs.",
-      "assertions": [
-        "Checks for product-marketing.md",
-        "Creates 5-7 email welcome sequence",
-        "Follows one email one job principle",
-        "Maps emails to trial timeline (14 days)",
-        "Includes timing between emails",
-        "Each email has hook, context, value, CTA",
-        "Includes subject lines for each email",
-        "Aligns with stated aha moment",
-        "Output follows structured per-email format"
-      ],
-      "files": []
-    },
-    {
-      "id": 2,
-      "prompt": "We need a lead nurture sequence for people who download our 'State of DevOps 2024' report. Goal is to get them to book a demo of our CI/CD platform.",
-      "expected_output": "Should create a lead nurture sequence (6-8 emails). Should follow value before ask — first emails should provide related value, not immediately push for demo. Should map the sequence from awareness (report download) through consideration (related content, case studies) to decision (demo request). Should include timing between emails. Each email should have clear subject line, hook, single CTA. Should gradually increase commitment asks across the sequence.",
-      "assertions": [
-        "Creates 6-8 email lead nurture sequence",
-        "Follows value before ask principle",
-        "Maps from awareness through consideration to decision",
-        "Includes timing between emails",
-        "Each email has clear subject line and single CTA",
-        "Gradually increases commitment asks",
-        "Connects to original download topic"
-      ],
-      "files": []
-    },
-    {
-      "id": 3,
-      "prompt": "our email open rates have tanked. used to be 35% now we're at 18%. what's going on and how do we fix our subject lines?",
-      "expected_output": "Should trigger on casual phrasing. Should diagnose potential causes of declining open rates: sender reputation, list hygiene, subject line quality, sending frequency, deliverability issues. Should apply the subject line strategy from the skill: test curiosity vs benefit vs urgency patterns, personalization, optimal length. Should recommend a re-engagement campaign to clean the list. Should provide specific subject line formulas and examples. Should suggest testing framework for subject lines.",
-      "assertions": [
-        "Triggers on casual phrasing",
-        "Diagnoses potential causes beyond just subject lines",
-        "Addresses sender reputation and deliverability",
-        "Recommends list hygiene or re-engagement",
-        "Applies subject line strategy with specific patterns",
-        "Provides subject line formulas and examples",
-        "Suggests testing framework"
-      ],
-      "files": []
-    },
-    {
-      "id": 4,
-      "prompt": "Build a re-engagement sequence for subscribers who haven't opened any emails in 90 days. We have about 5,000 inactive subscribers.",
-      "expected_output": "Should create a re-engagement sequence (3-4 emails). Should follow the re-engagement pattern: first email acknowledges absence and offers value, middle emails escalate with compelling reasons to re-engage, final email is a clear 'last chance' before removal. Should recommend aggressive subject lines to break through. Should include a sunset policy (remove non-responders after sequence completes). Should address the impact on deliverability of keeping inactive subscribers.",
-      "assertions": [
-        "Creates 3-4 email re-engagement sequence",
-        "Acknowledges absence in first email",
-        "Escalates through the sequence",
-        "Includes 'last chance' final email",
-        "Recommends sunset policy for non-responders",
-        "Addresses deliverability impact of inactive subscribers",
-        "Uses compelling subject lines"
-      ],
-      "files": []
-    },
-    {
-      "id": 5,
-      "prompt": "What's the ideal timing for our onboarding email sequence? We send the first email immediately after signup, but we're not sure about the rest.",
-      "expected_output": "Should provide timing guidance for onboarding sequences. Should reference the timing and delays framework: immediate first email (welcome/confirmation), then suggest data-driven timing based on user behavior triggers vs fixed time delays. Should recommend behavior-triggered emails when possible (user completed action → next email) with time-based fallbacks. Should provide typical timing patterns for SaaS onboarding (day 0, day 1, day 3, day 5, day 7, etc.). Should note that optimal timing depends on product complexity and trial length.",
-      "assertions": [
-        "Provides timing guidance for onboarding sequences",
-        "Recommends immediate first email",
-        "Discusses behavior-triggered vs time-based timing",
-        "Provides typical timing patterns",
-        "Notes timing depends on product and trial length",
-        "Recommends behavior triggers with time-based fallbacks"
-      ],
-      "files": []
-    },
-    {
-      "id": 6,
-      "prompt": "Help me optimize our post-signup onboarding experience. Users sign up but 60% never complete setup.",
-      "expected_output": "Should recognize this is an in-app onboarding optimization task, not an email sequence task. Should defer to or cross-reference the onboarding skill, which handles in-app onboarding flows, checklists, and activation optimization. May offer to help with the email component of onboarding but should make clear that onboarding is the primary skill for this task.",
-      "assertions": [
-        "Recognizes this as in-app onboarding optimization",
-        "References or defers to onboarding skill",
-        "Does not attempt full onboarding redesign using email patterns",
-        "May offer email component support"
-      ],
-      "files": []
-    }
-  ]
-}