Skip to content

aiskillstore/marketplace / skills/aayushbaniya2006/plans-handler

plans-handler

Verified

Manage subscription plans, pricing, and quotas. Use when adding plan features, updating limits, or building pricing pages.

FileKindSize
SKILL.mdskill md938 B
reference.mdmarkdown770 B
skill-report.jsonconfig14.3 KB

skill-report.json

View on GitHub
{
  "schema_version": "2.0",
  "meta": {
    "generated_at": "2026-07-06T00:57:58.767Z",
    "slug": "aayushbaniya2006-plans-handler",
    "source_url": "https://github.com/AayushBaniya2006/blinkfund/tree/main/.claude/skills/plans-handler",
    "source_ref": "main",
    "model": "codex",
    "analysis_version": "3.0.0",
    "source_type": "community",
    "content_hash": "df12712940c9ab49cfbb071167a8152a20bfba738f81d640681f7cc7ef337b83",
    "tree_hash": "f1be4653ea1bf215ea54a1b9582a6eb6e69d221d13389a03897358745ca2e3ee",
    "provenance": {
      "model_requested": "gpt-5.5:high",
      "model_effective": "codex:gpt-5.5:high",
      "fallback_chain": [
        {
          "agent": "codex",
          "model": "gpt-5.5",
          "effort": "high",
          "outcome": "success"
        }
      ],
      "analysis_version": "3.0.0"
    }
  },
  "skill": {
    "name": "plans-handler",
    "description": "Manage subscription plan schemas, quota validation, pricing tables, and current-plan access patterns for app development.",
    "summary": "Guides subscription plan, quota, pricing table, and current-plan changes across an app.",
    "icon": "📦",
    "version": "1.0.0",
    "author": "AayushBaniya2006",
    "license": "MIT",
    "tags": [
      "subscription-plans",
      "pricing",
      "quotas",
      "billing",
      "schema-sync"
    ],
    "supported_tools": [
      "claude",
      "codex",
      "claude-code"
    ],
    "risk_factors": [
      "external_commands"
    ],
    "category": "coding"
  },
  "security_audit": {
    "risk_level": "safe",
    "is_blocked": false,
    "safe_to_publish": true,
    "analysis_status": "ok",
    "summary": "The eight static findings are false positives caused by Markdown inline code spans in SKILL.md. No evidence found of prompt injection, data exfiltration, network access, or executable command instructions.",
    "remediation": [],
    "risk_factor_evidence": [
      {
        "factor": "external_commands",
        "evidence": [
          {
            "file": "SKILL.md",
            "line_start": 13,
            "line_end": 13
          },
          {
            "file": "SKILL.md",
            "line_start": 14,
            "line_end": 14
          },
          {
            "file": "SKILL.md",
            "line_start": 15,
            "line_end": 15
          },
          {
            "file": "SKILL.md",
            "line_start": 16,
            "line_end": 16
          },
          {
            "file": "SKILL.md",
            "line_start": 20,
            "line_end": 20
          },
          {
            "file": "SKILL.md",
            "line_start": 21,
            "line_end": 21
          },
          {
            "file": "SKILL.md",
            "line_start": 24,
            "line_end": 24
          },
          {
            "file": "SKILL.md",
            "line_start": 25,
            "line_end": 25
          }
        ]
      }
    ],
    "static_findings": [
      {
        "id": "external_commands:SKILL.md:13:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 13,
        "line_end": 13,
        "snippet": "1.  **DB Schema**: Add field to `quotaSchema` in `src/db/schema/plans.ts`."
      },
      {
        "id": "external_commands:SKILL.md:14:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 14,
        "line_end": 14,
        "snippet": "2.  **Validation**: Add field to `planFormSchema` in `src/lib/validations/plan.schema.ts`."
      },
      {
        "id": "external_commands:SKILL.md:15:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 15,
        "line_end": 15,
        "snippet": "3.  **UI**: Add input to `src/components/forms/plan-form.tsx`."
      },
      {
        "id": "external_commands:SKILL.md:16:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 16,
        "line_end": 16,
        "snippet": "4.  **Data**: Ask user to update the plan via `/super-admin/plans` dashboard."
      },
      {
        "id": "external_commands:SKILL.md:20:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 20,
        "line_end": 20,
        "snippet": "2.  Use `getSubscribeUrl` for buttons."
      },
      {
        "id": "external_commands:SKILL.md:21:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 21,
        "line_end": 21,
        "snippet": "3.  Display features from `plan.quotas`."
      },
      {
        "id": "external_commands:SKILL.md:24:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 24,
        "line_end": 24,
        "snippet": "- **Client**: `useCurrentPlan()` (SWR)."
      },
      {
        "id": "external_commands:SKILL.md:25:ruby-shell-backtick-execution",
        "category": "external_commands",
        "severity": "medium",
        "pattern": "Ruby/shell backtick execution",
        "file": "SKILL.md",
        "line_start": 25,
        "line_end": 25,
        "snippet": "- **Server**: `withAuthRequired` wrapper -> `getCurrentPlan()`."
      }
    ],
    "finding_verdicts": [
      {
        "id": "external_commands:SKILL.md:13:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.95,
        "reason": "Line 13 is a Markdown checklist item that wraps a schema name and file path in inline code. It does not instruct execution of a shell or Ruby command."
      },
      {
        "id": "external_commands:SKILL.md:14:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.95,
        "reason": "Line 14 uses Markdown inline code for a validation schema and file path. There is no command invocation, interpolation, or user-controlled execution path."
      },
      {
        "id": "external_commands:SKILL.md:15:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.95,
        "reason": "Line 15 is a prose reference to a UI file path formatted with Markdown backticks. It contains no executable shell command or automation step."
      },
      {
        "id": "external_commands:SKILL.md:16:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.95,
        "reason": "Line 16 names a dashboard route in Markdown inline code and asks the user to update data manually. It is not command execution."
      },
      {
        "id": "external_commands:SKILL.md:20:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.95,
        "reason": "Line 20 references a helper function name in Markdown inline code. It does not call an external command or describe shell execution."
      },
      {
        "id": "external_commands:SKILL.md:21:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.95,
        "reason": "Line 21 references a plan property in Markdown inline code. This is documentation formatting, not Ruby shell backtick execution."
      },
      {
        "id": "external_commands:SKILL.md:24:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.95,
        "reason": "Line 24 names a client hook in Markdown inline code. No shell command, subprocess, or dynamic execution behavior is present."
      },
      {
        "id": "external_commands:SKILL.md:25:ruby-shell-backtick-execution",
        "verdict": "false_positive",
        "confidence": 0.95,
        "reason": "Line 25 names server helpers in Markdown inline code. The text documents application helpers and does not execute an external command."
      }
    ],
    "semantic_findings": [],
    "critical_findings": [],
    "high_findings": [],
    "medium_findings": [],
    "low_findings": [],
    "dangerous_patterns": [],
    "files_scanned": 2,
    "total_lines": 51,
    "audit_model": "codex",
    "audited_at": "2026-07-06T00:57:58.767Z",
    "agent_auto_install_policy": "allowed",
    "manual_install_policy": "allowed"
  },
  "content": {
    "user_title": "Manage Subscription Plans and Quotas",
    "value_statement": "Plan and quota changes often touch schemas, validation, forms, pricing pages, and subscription flows. This skill gives Claude, Codex, and Claude Code a focused checklist for keeping those parts aligned.",
    "seo_keywords": [
      "Claude",
      "Codex",
      "Claude Code",
      "subscription plans",
      "pricing table",
      "quota management",
      "plan schema",
      "billing workflow",
      "SaaS plans",
      "super admin dashboard"
    ],
    "actual_capabilities": [
      "Identifies files to update when adding a new quota field.",
      "Guides updates to database schema, validation schema, and plan form.",
      "Explains how to build pricing tables from plan API data.",
      "Directs subscription buttons to use the subscription URL helper.",
      "Shows client and server helpers for reading the current plan.",
      "Points authors to the included plan architecture reference."
    ],
    "limitations": [
      "Does not include executable scripts or automated migrations.",
      "Assumes the target project uses the file paths named in the skill.",
      "Requires users to update plan data through the super admin dashboard.",
      "Does not validate provider billing IDs by itself."
    ],
    "use_cases": [
      {
        "title": "Add a quota field",
        "description": "Coordinate schema, validation, form, and dashboard changes for a new plan limit.",
        "target_user": "Full-stack developer"
      },
      {
        "title": "Build a pricing page",
        "description": "Create a pricing table that fetches plans and sends users through the subscription flow.",
        "target_user": "Frontend developer"
      },
      {
        "title": "Review plan access",
        "description": "Check client and server patterns for reading the active user subscription plan.",
        "target_user": "Backend developer"
      }
    ],
    "prompt_templates": [
      {
        "title": "Find Plan Files",
        "scenario": "Beginner discovery before editing plan quotas.",
        "prompt": "Use the plans-handler skill. Show me which project files must change before I add a new quota named images."
      },
      {
        "title": "Add a Quota Workflow",
        "scenario": "Guided implementation for a new plan limit.",
        "prompt": "Use the plans-handler skill. Help me add a storage quota and keep the schema, validation, form, and dashboard steps aligned."
      },
      {
        "title": "Create Pricing Table",
        "scenario": "Build a subscription pricing view.",
        "prompt": "Use the plans-handler skill. Plan a pricing table that fetches available plans, lists quotas, and routes subscribe buttons correctly."
      },
      {
        "title": "Audit Plan Consistency",
        "scenario": "Advanced review across subscription plan surfaces.",
        "prompt": "Use the plans-handler skill. Review my subscription plan changes for mismatched quotas, missing provider IDs, and incorrect current-plan access patterns."
      }
    ],
    "output_examples": [
      {
        "input": "Add a new images quota to the subscription plans.",
        "output": "A checklist covering database schema, validation, form updates, and the required dashboard data update."
      },
      {
        "input": "Build a pricing table for available plans.",
        "output": "A plan for fetching plans, showing quota features, and routing subscription buttons through the approved helper."
      },
      {
        "input": "Check how the app reads the current plan.",
        "output": "A review of the client hook and server helper patterns used for current-plan access."
      }
    ],
    "best_practices": [
      "Keep database, validation, and form fields in sync for every quota change.",
      "Use the super admin dashboard as the source of truth for plan data.",
      "Confirm provider IDs are present before exposing paid plan actions."
    ],
    "anti_patterns": [
      "Adding quota fields in the UI without matching schema changes.",
      "Manually seeding plan data when the dashboard should manage it.",
      "Hardcoding subscription links instead of using the subscription URL helper."
    ],
    "faq": [
      {
        "question": "What does this skill help manage?",
        "answer": "It helps manage subscription plan schemas, quotas, pricing tables, and current-plan access patterns."
      },
      {
        "question": "Does it run migrations automatically?",
        "answer": "No. It provides guidance and checklists, but it does not execute migrations or scripts."
      },
      {
        "question": "Can it build a pricing page?",
        "answer": "Yes. It outlines fetching plans, displaying quota features, and using the subscription URL helper."
      },
      {
        "question": "How should plan data be updated?",
        "answer": "Plan data should be updated through the super admin dashboard, which the skill treats as the source of truth."
      },
      {
        "question": "Which assistants can use this skill?",
        "answer": "The report lists support for Claude, Codex, and Claude Code."
      },
      {
        "question": "What should users verify after changes?",
        "answer": "Users should verify schema alignment, visible quota labels, subscription links, and provider billing IDs."
      }
    ]
  },
  "file_structure": [
    {
      "name": "reference.md",
      "type": "file",
      "path": "reference.md",
      "lines": 21
    },
    {
      "name": "SKILL.md",
      "type": "file",
      "path": "SKILL.md",
      "lines": 30
    }
  ]
}
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall