originality-check

Featured

Guideline-4.3 anti-spam / originality gate — score whether an app (and each portfolio addition) is meaningfully distinct in function, content, and metadata before you invest or submit. Use at validation/new-app time and again before submission. Protects the whole developer account from 4.3 (spam/duplicate) rejections. NOT rejection-handler (that works an existing rejection) and NOT competitive-analysis (that positions in the market).

AI & Automation 719 stars 68 forks Updated 1 months ago MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
95
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Originality Check Decide, with evidence, whether an app is *distinct enough to exist* — before you build it or submit it. > At portfolio scale, shipping many similar small apps risks **Guideline 4.3 (spam / duplicate)** > — this is the go/no-go distinctness gate that keeps that from happening. ## Where it fits (read the seams) - **Not `rejection-handler`.** That works a rejection you *already have*. This is upstream — it prevents the 4.3 by catching sameness before you ship. - **Not `competitive-analysis` / `market-research`.** Those size demand and position you in the market. This judges *distinctness* (function + content + metadata) vs your own portfolio and vs near-identical competitors — a spam risk, not a demand question. - **Two moments to run it:** at `validate` / `new-app` (don't build a dup) and before `submit` (don't trip 4.3). Also periodically across the portfolio (internal cannibalization / template-sameness). ## Prerequisites - The app idea or a shipped app to evaluate (name, one-line function, target metadata). - Optional: `.planning/VALIDATION.md` (competitor + market data). If missing/stale, gather fresh via WebSearch or the `product/competitive-analysis` skill. - Optional ASC access to read the developer's existing portfolio (`list_apps` / `get_metadata`). ## Flow 1. **Internal check (your own portfolio).** `list_apps` → for each shipped app read its positioning (`get_metadata`). Does the candidate overlap one you already ship in **fun...

Details

Author
rshankras
Repository
rshankras/claude-code-apple-skills
Created
10 months ago
Last Updated
1 months ago
Language
Swift
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

originality-review

Audit a website, interface, campaign, document, media artifact, or code-backed experience against supplied references for originality risk, source overlap, and asset provenance. Use when asked whether work copies its inspiration; to compare text, brands, numbers, images, video, layout, motion, code, fonts, icons, or other assets; inspect current and historical files; check credits or licenses; recommend replacements; or make a release verdict. Produces evidence-backed risk findings, not a legal conclusion.

0 Updated 4 days ago
sebastian-software
AI & Automation Listed

prior-art

Scan the open-source / research landscape for projects doing what this repo does — is anyone ahead of us, has anyone had our ideas, and what are they doing that's worth porting in. Use when the user says 'prior art scan', 'who else is doing this', 'has anyone built this', 'are we still novel', 'competitive scan of this repo', or wants a novelty check on a project's distinctive ideas. Produces a pillar table, a novelty verdict, a steal list, and a watch list.

0 Updated 1 weeks ago
dylanpulver
Code & Development Listed

priorart

Prior-art check before you build — does this idea already exist? Takes a project/tool/library idea, reframes it in the vocabularies different communities would use, searches where builders publish (code registries, Show HN, arXiv), traces each match one dependency-layer down to the real incumbent, and returns a locator-backed landscape plus exactly one verdict: Build / Fork X / Contribute to Y / Use Z / Investigate first. Checked ideas persist in out/priorart/checked.md, so re-checking one opens with what changed. Keyless. Use for "does something like X already exist", "has anyone built this", "am I reinventing the wheel", "check prior art before I build" — e.g. "/priorart <idea>". For your existing project vs its peers use scout; for choosing between named options use verdict.

9 Updated 3 days ago
duthaho