[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H7448KECN4VGPEEHGFGR95":3,"skill-same:01M6H7448KECN4VGPEEHGFGR95":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6H7448KECN4VGPEEHGFGR95","instantly-cost-tuning",null,"Optimize Instantly costs through tier selection, sampling, and usage monitoring.\nUse when analyzing Instantly billing, reducing API costs,\nor implementing usage monitoring and budget alerts.\nTrigger with phrases like \"instantly cost\", \"instantly billing\",\n\"reduce instantly costs\", \"instantly pricing\", \"instantly expensive\", \"instantly budget\".","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Finstantly-pack\u002Fskills\u002Finstantly-cost-tuning\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"tuning","instantly cost tuning","cost","optimize","reduce","implementing","usage","with","billing","trigger","io","alerts","codex","selection","sampling","use","api","monitoring","code","pricing","2026-11-10 10:12:30",false,"---\nname: instantly-cost-tuning\ndescription: |\n  Optimize Instantly costs through tier selection, sampling, and usage monitoring.\n  Use when analyzing Instantly billing, reducing API costs,\n  or implementing usage monitoring and budget alerts.\n  Trigger with phrases like \"instantly cost\", \"instantly billing\",\n  \"reduce instantly costs\", \"instantly pricing\", \"instantly expensive\", \"instantly budget\".\nallowed-tools: Read, Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\n---\n# Instantly Cost Tuning\n\n## Overview\nOptimize Instantly email outreach costs by managing sending account count, right-sizing your plan tier, and maximizing deliverability (which is the core ROI metric). Instantly pricing combines per-seat costs with sending volume tiers (Growth: 5K leads\u002Fmonth, Hypergrowth: 25K leads\u002Fmonth, Light Speed: 100K leads\u002Fmonth).\n\n## Prerequisites\n- Instantly workspace admin access\n- Sending account reputation data\n- Campaign performance analytics\n\n## Instructions\n\n### Step 1: Audit Account Efficiency\n```bash\nset -euo pipefail\n# Check per-account performance\ncurl \"https:\u002F\u002Fapi.instantly.ai\u002Fapi\u002Fv1\u002Faccount\u002Fstatus\" \\\n  -H \"Authorization: Bearer $INSTANTLY_API_KEY\" | \\\n  jq '.accounts[] | {\n    email, daily_limit, sent_today,\n    reputation_score, warmup_status,\n    effective_sends: (.sent_today * .reputation_score \u002F 100)\n  }' | jq -s 'sort_by(-.effective_sends)'\n# Accounts with low reputation are wasting sends (emails go to spam)\n```\n\n### Step 2: Consolidate Sending Accounts\n```yaml\n# Before: 10 accounts, each sending 30 emails\u002Fday = 300 sends\u002Fday\n# Problem: 4 accounts have \u003C50 reputation score (emails going to spam)\ncurrent:\n  accounts: 10\n  effective_sends_per_day: 180  # Only 6 accounts delivering well\n  monthly_cost: \"$97\u002Fmonth per account subscription\"\n\noptimized:\n  accounts: 6               # Remove low-reputation accounts\n  effective_sends_per_day: 180  # Same effective volume\n  monthly_cost: \"58% of original\"\n```\n\n### Step 3: Optimize Warmup Strategy\n```yaml\n# Proper warmup maximizes deliverability, which maximizes ROI\nwarmup_best_practices:\n  new_account:\n    week_1: 5 emails\u002Fday      # Start very low\n    week_2: 15 emails\u002Fday\n    week_3: 30 emails\u002Fday\n    week_4: 50 emails\u002Fday     # Full sending capacity\n    total_warmup: 28 days\n\n  # Don't rush warmup to save time -- a burnt account costs more to replace\n  # than 4 weeks of gradual warmup\n\n  monitoring:\n    check_daily: reputation_score\n    pause_if: reputation_score \u003C 60\n    reduce_volume_if: bounce_rate > 3%\n```\n\n### Step 4: Right-Size Your Plan\n```yaml\n# Plan selection based on actual sending needs\ngrowth_plan:\n  leads: 5000\u002Fmonth  # 5000: 5 seconds in ms\n  best_for: \"Small team, 1-2 SDRs, testing campaigns\"\n  cost: \"$37\u002Fmonth\"\n\nhypergrowth_plan:\n  leads: 25000\u002Fmonth  # 25000 = configured value\n  best_for: \"Active outbound team, 3-5 SDRs\"\n  cost: \"$97\u002Fmonth\"\n  tip: \"Only upgrade when Growth plan consistently hits >80% lead capacity\"\n\n# Calculate: if you're on Hypergrowth but only importing 3K leads\u002Fmonth,\n# switch to Growth and save $60\u002Fmonth\n```\n\n### Step 5: Improve Reply Rate (Best ROI Optimization)\n```yaml\n# The highest ROI optimization is improving reply rate, not sending more emails\noptimization_priority:\n  1_clean_lead_lists:\n    action: \"Verify emails before importing\"\n    impact: \"Reduces bounces, protects reputation, fewer wasted sends\"\n  2_personalize_sequences:\n    action: \"Use merge tags and custom variables\"\n    impact: \"2-3x reply rate improvement\"\n  3_optimize_sending_schedule:\n    action: \"Send Tuesday-Thursday 9-11am recipient timezone\"\n    impact: \"20-30% better open rates\"\n  4_a_b_test_subject_lines:\n    action: \"Test 2-3 variants per campaign\"\n    impact: \"10-20% open rate improvement\"\n```\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Paying for unused sending capacity | Plan oversized for actual volume | Downgrade plan tier |\n| Low ROI per dollar spent | Poor deliverability | Fix warmup, clean lists, improve personalization |\n| Account costs without results | Account reputation too low | Pause account, rewarm or replace domain |\n| High bounce rate | Unverified lead lists | Use email verification before import |\n\n## Examples\n\n**Basic usage**: Apply instantly cost tuning to a standard project setup with default configuration options.\n\n**Advanced scenario**: Customize instantly cost tuning for production environments with multiple constraints and team-specific requirements.\n\n## Output\n\n- Configuration files or code changes applied to the project\n- Validation report confirming correct implementation\n- Summary of changes made and their rationale\n\n## Resources\n\n- Official monitoring documentation\n- Community best practices and patterns\n- Related skills in this plugin pack","# Instantly Cost Tuning\n\n## Overview\nOptimize Instantly email outreach costs by managing sending account count, right-sizing your plan tier, and maximizing deliverability (which is the core ROI metric). Instantly pricing combines per-seat costs with sending volume tiers (Growth: 5K leads\u002Fmonth, Hypergrowth: 25K leads\u002Fmonth, Light Speed: 100K leads\u002Fmonth).\n\n## Prerequisites\n- Instantly workspace admin access\n- Sending account reputation data\n- Campaign performance analytics\n\n## Instructions\n\n### Step 1: Audit Account Efficiency\n```bash\nset -euo pipefail\n# Check per-account performance\ncurl \"https:\u002F\u002Fapi.instantly.ai\u002Fapi\u002Fv1\u002Faccount\u002Fstatus\" \\\n  -H \"Authorization: Bearer $INSTANTLY_API_KEY\" | \\\n  jq '.accounts[] | {\n    email, daily_limit, sent_today,\n    reputation_score, warmup_status,\n    effective_sends: (.sent_today * .reputation_score \u002F 100)\n  }' | jq -s 'sort_by(-.effective_sends)'\n# Accounts with low reputation are wasting sends (emails go to spam)\n```\n\n### Step 2: Consolidate Sending Accounts\n```yaml\n# Before: 10 accounts, each sending 30 emails\u002Fday = 300 sends\u002Fday\n# Problem: 4 accounts have \u003C50 reputation score (emails going to spam)\ncurrent:\n  accounts: 10\n  effective_sends_per_day: 180  # Only 6 accounts delivering well\n  monthly_cost: \"$97\u002Fmonth per account subscription\"\n\noptimized:\n  accounts: 6               # Remove low-reputation accounts\n  effective_sends_per_day: 180  # Same effective volume\n  monthly_cost: \"58% of original\"\n```\n\n### Step 3: Optimize Warmup Strategy\n```yaml\n# Proper warmup maximizes deliverability, which maximizes ROI\nwarmup_best_practices:\n  new_account:\n    week_1: 5 emails\u002Fday      # Start very low\n    week_2: 15 emails\u002Fday\n    week_3: 30 emails\u002Fday\n    week_4: 50 emails\u002Fday     # Full sending capacity\n    total_warmup: 28 days\n\n  # Don't rush warmup to save time -- a burnt account costs more to replace\n  # than 4 weeks of gradual warmup\n\n  monitoring:\n    check_daily: reputation_score\n    pause_if: reputation_score \u003C 60\n    reduce_volume_if: bounce_rate > 3%\n```\n\n### Step 4: Right-Size Your Plan\n```yaml\n# Plan selection based on actual sending needs\ngrowth_plan:\n  leads: 5000\u002Fmonth  # 5000: 5 seconds in ms\n  best_for: \"Small team, 1-2 SDRs, testing campaigns\"\n  cost: \"$37\u002Fmonth\"\n\nhypergrowth_plan:\n  leads: 25000\u002Fmonth  # 25000 = configured value\n  best_for: \"Active outbound team, 3-5 SDRs\"\n  cost: \"$97\u002Fmonth\"\n  tip: \"Only upgrade when Growth plan consistently hits >80% lead capacity\"\n\n# Calculate: if you're on Hypergrowth but only importing 3K leads\u002Fmonth,\n# switch to Growth and save $60\u002Fmonth\n```\n\n### Step 5: Improve Reply Rate (Best ROI Optimization)\n```yaml\n# The highest ROI optimization is improving reply rate, not sending more emails\noptimization_priority:\n  1_clean_lead_lists:\n    action: \"Verify emails before importing\"\n    impact: \"Reduces bounces, protects reputation, fewer wasted sends\"\n  2_personalize_sequences:\n    action: \"Use merge tags and custom variables\"\n    impact: \"2-3x reply rate improvement\"\n  3_optimize_sending_schedule:\n    action: \"Send Tuesday-Thursday 9-11am recipient timezone\"\n    impact: \"20-30% better open rates\"\n  4_a_b_test_subject_lines:\n    action: \"Test 2-3 variants per campaign\"\n    impact: \"10-20% open rate improvement\"\n```\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Paying for unused sending capacity | Plan oversized for actual volume | Downgrade plan tier |\n| Low ROI per dollar spent | Poor deliverability | Fix warmup, clean lists, improve personalization |\n| Account costs without results | Account reputation too low | Pause account, rewarm or replace domain |\n| High bounce rate | Unverified lead lists | Use email verification before import |\n\n## Examples\n\n**Basic usage**: Apply instantly cost tuning to a standard project setup with default configuration options.\n\n**Advanced scenario**: Customize instantly cost tuning for production environments with multiple constraints and team-specific requirements.\n\n## Output\n\n- Configuration files or code changes applied to the project\n- Validation report confirming correct implementation\n- Summary of changes made and their rationale\n\n## Resources\n\n- Official monitoring documentation\n- Community best practices and patterns\n- Related skills in this plugin pack",{"name":5,"author":43,"license":14,"version":44,"description":45,"allowed-tools":46,"compatible-with":47},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Optimize Instantly costs through tier selection, sampling, and usage monitoring.\nUse when analyzing Instantly billing, reducing API costs,\nor implementing usage monitoring and budget alerts.\nTrigger with phrases like \"instantly cost\", \"instantly billing\",\n\"reduce instantly costs\", \"instantly pricing\", \"instantly expensive\", \"instantly budget\".\n","Read, Grep","claude-code, codex, openclaw","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","claude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Finstantly-pack\u002Fskills\u002Finstantly-cost-tuning",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add micsapp\u002Fmicstec-skills --skill instantly-cost-tuning",{"tool":61,"command":62},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill instantly-cost-tuning",{"tool":64,"command":65},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill instantly-cost-tuning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Finstantly-pack\u002Fskills\u002Finstantly-cost-tuning\u002FSKILL.md",true,[],[70,105,133,153,173,198],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":86,"publishedAt":38},"01M6HBTJ02FXBFG9NYEHHYAP52","azure-apim-architecture","Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[76,81],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[87,88,89,90,91,92,93,94,95,34,96,97,98,99,100,31,101,102,103,104],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","team","environment","multi-environment","workspaces","instances","strategies","azure api management","mode","for",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":119,"publishedAt":38},"01M6HBT7J4H082JEEA670B3EQ9","apiops-deployment","Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep\u002FTerraform), CI\u002FCD pipelines (GitHub Actions\u002FAzure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapiops-deployment\u002FSKILL.md",[111,112,115,118],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},{"categoryNo":113,"categoryName":114,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":116,"categoryName":117,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[120,121,122,123,88,124,36,125,126,127,128,129,34,96,101,130,131,102,132,23],"deployment","apiops deployment","workflows","azure devops","infrastructure","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":140,"publishedAt":38},"01M6HBT2HEA23THNE9E00GYQBE","apim-policy-authoring","Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request\u002Fresponse processing logic.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapim-policy-authoring\u002FSKILL.md",[139],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[141,142,143,144,88,91,34,96,145,33,146,147,148,149,150,102,151,152,23,104],"policy","authoring","apim policy authoring","security","access","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":161,"publishedAt":38},"01M6HBSY65SB29J9WE9KYD0K6T","api-security-review","Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapi-security-review\u002FSKILL.md",[159,160],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[162,144,163,34,147,164,88,120,165,166,167,168,96,169,102,170,171,172,103,104],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":38},"01M6HBSRW4PDFE6K4F8JYPZQ05","jira-cli","Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fjira-cli\u002FSKILL.md",[],[180,181,182,122,183,184,185,186,34,187,188,189,190,191,192,193,194,195,196,197],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","edit","list","view","project","project work","token","line","sprints",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":204,"publishedAt":38},"01M6HBSNS3JHMW603G47TWE31H","calculator","Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fcalculator\u002FSKILL.md",[],[200,205,206,207,208,209,210,33,211,212],"npm","js","calculate","node","math","user","compute","errors"]