Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Loyalty Program Design

ASecurity

Draft a loyalty program structure that rewards the behavior the brand actually wants to drive. Use when the user mentions loyalty program, rewards program, points program, customer loyalty retail, or asks for a loyalty program brief. Retail and commerce skill by Yasir Jilani.

2 stars
0 votes
0 copies
0 views
Added 9/30/2026
ai-agentspythongoawsgitapi

Works with

cliapi

Security Analysis

A100/100

Scanned 9/30/2026

$npx -y skills add SYasJ/claude-business-skills --skill loyalty-program-design --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Loyalty Program Design?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Loyalty Program Design
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/syasj-loyalty-program-design/badge)](https://www.skillsdirectory.com/skills/syasj-loyalty-program-design)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: loyalty-program-design
description: "Draft a loyalty program structure that rewards the behavior the brand actually wants to drive. Use when the user mentions loyalty program, rewards program, points program, customer loyalty retail, or asks for a loyalty program brief. Retail and commerce skill by Yasir Jilani."
license: MIT
compatibility: Agent Skills standard. No network access, extra packages, or credentials required.
metadata:
  author: Yasir Jilani
  version: "1.0.0"
  domain: retail
---

<!-- GENERATED FILE - edits here are overwritten by scripts/generate.py.
     Edit the 'loyalty-program-design' entry in source/, then run:
       python3 scripts/generate.py && python3 scripts/validate.py
     See CONTRIBUTING.md. -->

# Loyalty Program Design

Draft a loyalty program structure that rewards the behavior the brand actually wants to drive.

## When to use this skill

Use this skill when the user:

- loyalty program
- rewards program
- points program
- customer loyalty retail

## When not to use this skill

- The user wants a different domain's specialist skill.
- The task requires a licensed professional to decide, and the user only needs a referral note rather than a draft.
- The request asks you to deceive, evade a control, or hide material facts.

## Professional boundary

Do not invent inventory, prices, or reviews. Do not write deceptive promotions.

## Operating boundaries

- Use only information the user provides or files they explicitly ask you to read. Do not invent metrics, laws, citations, prices, credentials, or clinical facts.
- Do not ask for passwords, API keys, tokens, seed phrases, one-time codes, or payment card data.
- Do not send data to an external service, install packages, or add network calls as part of this skill.
- Separate facts, assumptions, and recommendations. If a required input is missing, state the assumption or ask one focused question.
- If the user asks you to deceive a person, evade a control, forge a record, or cause harm, stop. Offer a legitimate alternative.
- Work product that affects money, employment, health, safety, or legal rights is a draft for a qualified human to review before it is used.

## Inputs to collect

- What behavior they want to reward
- Their margin
- Tech they have
- Competitors they named

## Workflow


### 1. Step 1

Define the earn rule from the behavior they want, not from the points chart that sounds nice.
### 2. Step 2

State the redemption value in real dollars so they can check the margin math.
### 3. Step 3

A high earn rate with a blocked redemption is a fraud risk. Do not design that.
### 4. Step 4

Cap liability exposure if they name a max outstanding balance.
### 5. Step 5

Name what happens to points on a return.
### 6. Step 6

This is a draft structure. They need legal review before launch.

## Output

Deliver a **loyalty program brief**.

- Purpose of this loyalty program brief, in two sentences.
- Facts the user supplied, listed separately from assumptions.
- The work itself, in the structure the workflow names.
- Open questions, risks, and the single next action with an owner.
- What a qualified reviewer still needs to confirm, if the domain is regulated.

## Quality bar

- Every number, date, name, and citation came from the user or is marked as an assumption.
- The artifact can be used without reading this skill again.
- Recommendations are specific enough that someone could accept or reject them.
- Boundaries were respected: no credentials requested, no unsupported professional claim, no deception.

## Example

### Scenario

Diane Cho, store lead at Harbor Goods in Airdrie, needs a loyalty program brief by 30 September 2026. A program offers 10% back in points but the redemption minimum is higher than the average order, so few members ever cash out.

### Example data

```text
From: Diane Cho, store lead
Organization: Harbor Goods, Airdrie
Date: 14 September 2026
Needed by: 30 September 2026

A program offers 10% back in points but the redemption minimum is higher than the average order, so few members ever cash out.

What behavior they want to reward: Returns desk log, last reviewed 14 September 2026. No owner named since
Their margin: End-cap display 3, last reviewed 14 September 2026. No owner named since
Tech they have: End-cap display 3. Partly documented: the what is written down, the who is not
Competitors they named: two deals cited from memory. Neither has a written loss reason
```

### Example outcome

**Loyalty program brief**
To: Diane Cho, store lead, Harbor Goods
Date: 14 September 2026 · Needed by: 30 September 2026

**Decision**
Sets a redemption minimum below the average order and discloses the liability cap.

**What the file supports**

| Input | Value | Status |
| --- | --- | --- |
| What behavior they want to reward | Returns desk log, last reviewed 14 September 2026. No owner named since | Needs confirmation |
| Their margin | End-cap display 3, last reviewed 14 September 2026. No owner named since | Carried into the draft |
| Tech they have | End-cap display 3. Partly documented: the what is written down, the who is not | Carried into the draft |
| Competitors they named | two deals cited from memory. Neither has a written loss reason | Needs confirmation |

**How this draft was built**

**1. Define the earn rule from the behavior they want, not from the points chart that sounds nice**

**2. State the redemption value in real dollars so they can check the margin math**

**3. A high earn rate with a blocked redemption is a fraud risk. Do not design that**

**4. Cap liability exposure if they name a max outstanding balance**

**5. Name what happens to points on a return**

**Deliberately not done**
- An earn rate that creates liability they cannot pay.
- Blocked redemption that misleads members.
- No return policy for points.

**Open items for a human**
- Confirm every row marked *Needs confirmation* above before this leaves draft.
- Anything absent from the file stayed absent. No figure, date, or name was supplied from outside it.

Next: Diane Cho by 30 September 2026. This is a draft, not a sign-off.

## Anti-patterns

- An earn rate that creates liability they cannot pay
- Blocked redemption that misleads members
- No return policy for points

## Related skills

- `promotion-review`
- `customer-health-score`

Attribution

SYasJSYasJ
View sourceSee grades on GitHubMore from SYasJ →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →