All authors

Claude Skills by greenfield-inc
github.com/greenfield-inc168 skills21 installs234 views
- Seo Briefing(proactive) Pull analytics from PostHog, GSC, and Ahrefs. Correlate data and produce an actionable SEO briefing. Use when the user wants an SEO status report, morning briefing, analytics overview, or wants to understand how their site is performing. Examples: 'SEO briefing', 'how is the site doing', 'pull analytics', 'morning report', 'check indexing status', 'what keywords are we ranking for'.Votes: 0GitHub stars: 9
- Seo Content Drafting(execution) Create new SEO content: blog posts, landing pages, comparison pages based on the content strategy. Use when the user wants to create new content for SEO: blog posts, landing pages, comparison pages, or category pages. Usually follows seo-content-strategy. Examples: 'write the blog posts', 'create the landing pages', 'draft the comparison page', 'fill the content calendar'.Votes: 0GitHub stars: 9
- Seo Data Organize(support) Archive and organize .seo/ data into a dated wiki structure for historical tracking. This is a support skill that runs at the end of any SEO workflow. It archives the current .seo/ working data into a dated, browsable wiki structure so nothing gets lost and you can track SEO progress over time. Other SEO skills should call this as their final step.Votes: 0GitHub stars: 9
- Seo Data Pull(support) Discover connected analytics sources, pull data, write .seo/data/ snapshots, and visualize results with deltas vs prior pulls. This is a support skill. Don't invoke it directly. Other SEO skills (seo-briefing, seo-readability-pass, seo-authority-pass, seo-content-strategy, seo-content-drafting) call it as their first step when they need fresh data. If .seo/data/ is stale or missing, any SEO skill should run this first.Votes: 0GitHub stars: 9
- Seo Foundations(greenfield) Crawl your site, find competitors, map the search landscape, and build the starting point for all SEO work. Use when starting SEO from scratch, onboarding a new site, or when the agent doesn't know what the product is, who the competitors are, or what keywords matter. This is the zeroth step before seo-briefing. Examples: 'start SEO from scratch', 'set up SEO for this site', 'who are our competitors', 'what should we rank for', 'SEO foundations', 'greenfield SEO'.Votes: 0GitHub stars: 9
- Seo Readability Pass(foundational) Audit and rewrite website copy for voice consistency, readability, and first-timer comprehension. Use when the user wants to improve the readability, voice, or comprehension of product website copy. Examples: 'do a readability pass', 'fix the copy', 'rewrite the docs to match my voice', 'the docs sound too technical', 'do a comprehension audit', 'humanity pass on the website'.Votes: 0GitHub stars: 9
- Seo Writing Framework(foundational) Research, draft, reader-hat, edit, slop-gate, score process for any customer-facing deliverable. Use when producing any customer-facing deliverable: pricing emails, blog posts, landing pages, docs, support replies, announcements, PR descriptions, onboarding copy, or any writing where the words matter. Can be invoked standalone or called by other SEO skills (readability, authority, drafting) as their writing process. Examples: 'write this email', 'draft this announcement', 'help...Votes: 0GitHub stars: 9
- Smell FinderSearch the default branch for one or two code-smell lenses from CRITERIA.md and return proven findings with file:line, read-only. Used by the finders that code-smell-fixes launches.Votes: 0GitHub stars: 9
- SwarmUse for research, audits, sweeps and code mapping where completeness matters. Split the territory into non-overlapping chunks, run one read-only agent per chunk in parallel, then reconcile every result against the code, the decisions, and each other.Votes: 0GitHub stars: 9
- Ui OptionsWhen the person dislikes how a piece of UI looks (often mid-QA), build three real design options in the actual code, screenshot each in the same set of states and contexts, share the folder, recommend one, then land the chosen option. Use for "I don't like this UI", "this looks off / not modern / cluttered", or "give me options for X" about an existing screen. For new screens that do not exist yet, use ui-mockup.Votes: 0GitHub stars: 9
- Ui PolishUse to polish the UI of an existing app (web, Electron or native) while it runs. Measure the hover, focus, press, hit-area and motion defects that screenshots miss, fix them at the narrowest level in code, and prove each fix with before and after screenshots.Votes: 0GitHub stars: 9
- Mac Security CheckRead-only security scan of the developer Mac you are running on, with a prioritized fix list and prune suggestions. Use when the person asks to check, audit, scan or harden their laptop or Mac, find unused attack surface, or run "mac-security-check". Changes nothing unless the person approves each command.Votes: 0GitHub stars: 9
- Windows Security CheckRead-only security scan of the Windows PC you are running on, with a prioritized fix list and prune suggestions. Use when the person asks to check, audit, scan or harden their Windows laptop or PC, find unused attack surface, or run "windows-security-check". Runs as a standard user and changes nothing unless the person approves each command.Votes: 0GitHub stars: 9
- Ios SimulatorsUse whenever you test or QA an iOS app on a simulator. Run slim simulators (SimSlim) so several fit on one Mac, one per agent or test shard, preflight them, and clean up after.Votes: 0GitHub stars: 9
- Android EmulatorsUse whenever you test or QA an Android app on an emulator. Pick the system image by whether the run needs screenshots, run emulators headless, one per agent or test shard, and clean up after.Votes: 0GitHub stars: 9
- Ios SimulatorsUse whenever you test or QA an iOS app on a simulator. Run slim simulators (SimSlim) so several fit on one Mac, one per agent or test shard, keep only the services the journeys need, preflight them, and clean up after.Votes: 0GitHub stars: 9
- Machine ResourcesUse whenever you create a VM, container, simulator or emulator, or launch Chrome for automation. Reuse what fits, size the work to the machine you are on, and delete what the run created when it ends.Votes: 0GitHub stars: 9
- Quick VerifyUse while working to confirm a change does what you meant before moving on. Observe its real effect the way a user or caller would, compare that with your intent, fix what is off, and observe again.Votes: 0GitHub stars: 9