diff --git a/docs/README.skills.md b/docs/README.skills.md index d7e9a764b..99bc7f8e0 100644 --- a/docs/README.skills.md +++ b/docs/README.skills.md @@ -333,6 +333,7 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to | [secret-scanning](../skills/secret-scanning/SKILL.md)
`gh skills install github/awesome-copilot secret-scanning` | Guide for configuring and managing GitHub secret scanning, push protection, custom patterns, and secret alert remediation. For pre-commit secret scanning in AI coding agents via the GitHub MCP Server, this skill references the Advanced Security plugin (`advanced-security@copilot-plugins`). Use this skill when enabling secret scanning, setting up push protection, defining custom patterns, triaging alerts, resolving blocked pushes, or when an agent needs to scan code for secrets before committing. | `references/alerts-and-remediation.md`
`references/custom-patterns.md`
`references/push-protection.md` | | [security-review](../skills/security-review/SKILL.md)
`gh skills install github/awesome-copilot security-review` | AI-powered codebase security scanner that reasons about code like a security researcher — tracing data flows, understanding component interactions, and catching vulnerabilities that pattern-matching tools miss. Use this skill when asked to scan code for security vulnerabilities, find bugs, check for SQL injection, XSS, command injection, exposed API keys, hardcoded secrets, insecure dependencies, access control issues, or any request like "is my code secure?", "review for security issues", "audit this codebase", or "check for vulnerabilities". Covers injection flaws, authentication and access control bugs, secrets exposure, weak cryptography, insecure dependencies, and business logic issues across JavaScript, TypeScript, Python, Java, PHP, Go, Ruby, and Rust. | `references/language-patterns.md`
`references/report-format.md`
`references/secret-patterns.md`
`references/vuln-categories.md`
`references/vulnerable-packages.md` | | [semantic-kernel](../skills/semantic-kernel/SKILL.md)
`gh skills install github/awesome-copilot semantic-kernel` | Create, update, refactor, explain, or review Semantic Kernel solutions using shared guidance plus language-specific references for .NET and Python. | `references/dotnet.md`
`references/python.md` | +| [sequenzy-email-marketing](../skills/sequenzy-email-marketing/SKILL.md)
`gh skills install github/awesome-copilot sequenzy-email-marketing` | Operate Sequenzy email marketing workflows safely: manage subscribers, segments, campaigns, sequences, templates, transactional email, account identity, API keys, and delivery stats with review-first defaults. Use when the user asks GitHub Copilot to work with Sequenzy email marketing or lifecycle automation. | None | | [shuffle-json-data](../skills/shuffle-json-data/SKILL.md)
`gh skills install github/awesome-copilot shuffle-json-data` | Shuffle repetitive JSON objects safely by validating schema consistency before randomising entries. | None | | [slang-shader-engineer](../skills/slang-shader-engineer/SKILL.md)
`gh skills install github/awesome-copilot slang-shader-engineer` | Use when working with Slang shaders, shader modules, HLSL-compatible GPU code, graphics pipelines, compute shaders, tessellation, ray tracing, parameter blocks, generics, interfaces, capabilities, cross-compilation, shader optimization, shader review, or C++ engine integration for Slang. Trigger on any mention of Slang, .slang files, slangc, SPIR-V from Slang, Slang modules, [shader("compute")], [shader("vertex")], or requests to write/review/refactor shader code with modern language features. Also trigger for Slang-to-HLSL/GLSL/Metal/CUDA cross-compile questions, or when the user says "shader" alongside "generics", "interfaces", "parameter blocks", "autodiff", or "capabilities". | `references/language-reference.md`
`references/rules-and-patterns.md`
`references/slang-documentation-full.md` | | [snowflake-semanticview](../skills/snowflake-semanticview/SKILL.md)
`gh skills install github/awesome-copilot snowflake-semanticview` | Create, alter, and validate Snowflake semantic views using Snowflake CLI (snow). Use when asked to build or troubleshoot semantic views/semantic layer definitions with CREATE/ALTER SEMANTIC VIEW, to validate semantic-view DDL against Snowflake via CLI, or to guide Snowflake CLI installation and connection setup. | None | diff --git a/skills/sequenzy-email-marketing/SKILL.md b/skills/sequenzy-email-marketing/SKILL.md new file mode 100644 index 000000000..248634708 --- /dev/null +++ b/skills/sequenzy-email-marketing/SKILL.md @@ -0,0 +1,76 @@ +--- +name: sequenzy-email-marketing +description: 'Operate Sequenzy email marketing workflows safely: manage subscribers, segments, campaigns, sequences, templates, transactional email, account identity, API keys, and delivery stats with review-first defaults. Use when the user asks GitHub Copilot to work with Sequenzy email marketing or lifecycle automation.' +metadata: + author: Sequenzy + version: '1.0' +compatibility: Works with GitHub Copilot agents and other SKILL.md-compatible coding agents. Requires access to a Sequenzy account, the Sequenzy CLI or API, and appropriate credentials. +--- + +# Sequenzy Email Marketing Skill + +Use this skill when the user asks you to operate Sequenzy email marketing workflows, including subscribers, lists, tags, segments, campaigns, sequences, templates, transactional email, websites, API keys, account identity, or delivery statistics. + +Canonical source: https://github.com/Sequenzy/skills/tree/main/skills/sequenzy-email-marketing + +## Safety Defaults + +- Prefer review-first workflows. Draft, preview, and return dashboard or review links before sending or activating anything. +- Verify account identity before mutations. Authenticate with `sequenzy login` for interactive work or `SEQUENZY_API_KEY` for automation, then verify the current account before changing data. +- Never invent subscriber IDs, campaign IDs, template IDs, API fields, or saved objects. Inspect current Sequenzy state or the canonical skill references first. +- Ask for explicit confirmation before sending campaigns, activating sequences, deleting resources, importing large lists, or rotating API keys. +- Redact API keys, tokens, and credentials in all output. + +## Common Workflows + +### Install the canonical skill + +```bash +npx skills add Sequenzy/skills --skill sequenzy-email-marketing +``` + +### Verify access + +```bash +sequenzy login +sequenzy whoami +sequenzy account +``` + +If the CLI is unavailable, use the Sequenzy API with `SEQUENZY_API_KEY`, but do not print the key. + +### Subscriber and segment work + +1. Inspect existing subscriber/list/tag/segment state before changing anything. +2. Add or update subscribers with the requested tags and attributes. +3. Return the saved subscriber profile or identifier. +4. For segments, preview or report the segment count before using it in a campaign. + +### Campaign, sequence, and template work + +1. Draft content and structure first. +2. Create or update the campaign, sequence, or template in draft/review mode when possible. +3. Return the review URL or saved object identifier. +4. Do not send or activate until the user explicitly approves. + +### Stats and recommendations + +When asked for performance analysis, read delivery/campaign stats, summarize the weakest points, and propose practical changes. Do not fabricate metrics if the API or CLI call fails. + +## Example Prompts + +```text +Use Sequenzy to draft a 4-email onboarding sequence for new trial users, then give me the dashboard URL to review it. +``` + +```text +Check last 30 days campaign stats, identify the weakest campaign, and suggest subject-line improvements without sending anything. +``` + +```text +Add user@example.com as a subscriber with the tags beta and founder, then show the saved subscriber profile. +``` + +## Boundaries + +Do not claim a send, activation, import, deletion, or API-key change happened unless you actually performed it and verified the result. If credentials, product access, or command/API details are missing, explain the blocker and stop before pretending success.