复制安装命令
用 Codex 或 Claude 安装复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它先审查 Skill 页面再帮你安装。
复制前请先查看来源、License 和安全提示。
🇧🇷 Versao em Portugues do Brasil
用 Codex 或 Claude 安装复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它先审查 Skill 页面再帮你安装。
复制前请先查看来源、License 和安全提示。
来源文件:README.md
🇧🇷 Versao em Portugues do Brasil
26 production-ready skills for AI coding agents. Install with one command, use across Claude Code, Cursor, Kiro, Windsurf, and OpenCode. Each skill teaches the agent to perform complex tasks — from rigorous engineering (pstack) to text humanization, SEO audits, and infrastructure automation.
Agent Skills are a lightweight, open format for extending AI agent capabilities. Each skill is a folder with a SKILL.md file containing metadata and instructions that agents load on demand. Learn more at agentskills.io.
data-fetching-and-analysisAnalyzes a startup idea through three lenses at once: Paul Graham (pressure test, founder-market fit, brutal validation), Dan Koe (monetization, offer, distribution, sales) and Seth Godin (differentiation, narrative, smallest viable audience). Delivers a pressure test, a monetization path, the minimum viable audience, a remarkability check and an action plan — not a generic canvas.
When to use: validate a startup idea, pressure-test a business model, define the MVP, find the first customers, design the revenue model, plan go-to-market, chase product-market fit, or any variation of "I have an idea".
code-quality-and-reviewOptimizes digital content and marketing strategies for Generative Engines (LLMs, AI agents) to maximize citations in AI responses.
When to use: improve visibility in AI responses (ChatGPT, Perplexity, Google AI Overview), measure citation rate, align terminology for LLMs, audit pages for AI, create optimized roundups and FAQs.
Improvements in v1.1 (Mar 2026):
references/guiding-principles.mdlibrary-and-api-referenceSubstack platform expert. Guides post formatting, SEO optimization (titles, slugs, meta descriptions), native engagement strategies (Notes, Chat), and conversion to paid subscriptions.
When to use: format and optimize Substack posts, improve newsletter SEO (titles, slugs, meta descriptions), grow audience with Notes and recommendations, convert free readers to paid subscribers, customize homepage and welcome emails.
Improvements in v1.1 (Mar 2026):
references/formatting-best-practices.mdreferences/seo-output-example.mdlibrary-and-api-referenceComplete guide to consuming the Pier Cloud (Lighthouse) API with authentication, context management, workspaces, and data views. Note: The documentation for this skill is in Portuguese, but it can be used in any language.
When to use: authenticate with Pier Cloud, list available contexts (AWS, etc), manage workspaces, access cost analysis views, run FinOps scripts.
Improvements in v1.1 (Mar 2026):
references/REFERENCE.mdcode-scaffolding-and-templatesGenerates Apple/Pentagram/frog/Vercel/Figma-level design deliverables using 10 specialized role-play prompts. Covers Design Systems, Brand Identity, UI/UX Patterns, Marketing Assets, Figma Specs, Design Critique, Trend Analysis, Accessibility Audit, Design-to-Code, and Executive Presentations.
When to use: create a design system, build brand identity, generate UI/UX patterns, produce marketing assets, write Figma specs, get design critique, analyze design trends, run accessibility audit, translate design to code, create presentation decks.
Improvements in v2.1 (Mar 2026):
references/briefing-questionnaire.mdImprovements in v2.2 (Mar 8, 2026):
This skill has been retired. The original project now offers 385 self-contained skills (one per rule) covering HTML, CSS, JavaScript, Performance, Accessibility, SEO, Security, Images, Testing, Privacy, and Internationalization — far more complete than what we maintained here.
👉 Install directly from: https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills
npx skills add frontendchecklist/skills
ci-cd-and-deploymentMaster operator for Coolify — the self-hosted open-source deployment platform (alternative to Heroku/Vercel/Netlify). Complete coverage of the official CLI with 100+ commands for managing applications, servers, databases, services, GitHub Apps, and cloud provider integrations.
When to use: connect to Coolify instances, create/deploy/restart/stop applications, manage environment variables and storage, configure database backups, list servers and databases, monitor deployment logs, manage multiple environments (dev/staging/prod), integrate with GitHub Apps, provision servers on Hetzner/DigitalOcean/Vultr.
Key features:
New in v2.0 (Aug 15, 2026):
app create (5 variants: public, github, deploy-key, dockerfile, dockerimage)app storage, app deployments, app previews, app tagsdatabase create/backup/storage/env/tags with full backup managementservice create --list-types, service application, service database sub-resourcesdeploy uuid/name/batch module with deploy list/get/cancelgithub list/get/create/update/delete/repos/branches for GitHub Appsprojects, resources, tags, destinations, cloud-token, private-keycode-scaffolding-and-templatesRewrites resumes for ATS compatibility and audits LinkedIn profiles for professional positioning. Covers CV optimization for Brazilian ATS platforms (Gupy, Vagas.com, PandaPé, Sólides) and LinkedIn audit with heuristic scoring, SSI analysis, fix prompts, and LLM rewrite mega-prompts. Works for any specialized profession — not dev-only.
When to use: optimize resume for ATS, audit LinkedIn profile (headline, about, experiences, SSI), adapt CV to target role/industry, generate fix prompts per finding, align CV and LinkedIn in unified mode, improve bullets with measurable outcomes. Integrates with humanizar skill for narrative sections.
Improvements in v2.0 (Jun 2026):
modo_linkedin (full profile audit with scoring) and modo_unificado (CV + LinkedIn with consistency check)humanizar skill (scoped to About/Summary sections)auditoria-linkedin.md, ssi.md, presets-formatos.mdproduct-verificationAudits any website for AI agent readiness using the Cloudflare isitagentready.com scanner. Scans 18 checks across 5 categories (Discoverability, Content, Bot Access Control, API/Auth/MCP Discovery, Commerce), assigns a level (0–5), and generates copy-paste fix prompts for every failing check. Includes 20 implementation sub-skills covering robots.txt, sitemap, Markdown for Agents, Content Signals, MCP Server Card, A2A Agent Card, Agent Skills Index, OAuth, WebMCP, and more.
When to use: scan a site for agent readiness, check agent-ready score, fix failing checks, implement MCP Server Card, add Content Signals, publish Agent Skills index, set up Markdown for Agents, batch scan multiple domains, improve AI agent discoverability.
product-verificationValidates DESIGN.md files against the official Google design.md specification using the @google/design.md CLI linter. Works with local files and remote URLs. Always uses npx to run the latest published version — never stale.
When to use: lint a DESIGN.md for spec compliance, check WCAG contrast ratios, find broken token references, diff two design system versions, export tokens to Tailwind v3/v4 or W3C DTCG format, audit frontmatter schema.
code-scaffolding-and-templatesAutomated iterative agent runner for spec-based development in Kiro. Wraps kiro-cli in a self-correcting bash loop that picks up tasks from a Kiro spec, implements them one at a time, verifies against exit criteria, and accumulates corrections and codebase patterns across iterations. Based on ralph-loop-kiro-specs by mreferre.
When to use: automate Kiro spec task implementation, run kiro-cli in a loop, drive a spec to completion through repeated agent iterations, set up or troubleshoot the Ralph Loop workflow, understand progress tracking, corrections, codebase patterns, and the summary dashboard.
code-scaffolding-and-templatesDesign well-structured agent loops with best-practice coaching and cross-model review gates before you run them. Interviews you, critiques your design against built-in rubrics, wires in reviewers/judges, and emits portable artifacts (loop.yaml, RUN_IN_SESSION.md, run-loop.py). Integrates natively with Kiro CLI's /goal and subagent review loops. Based on Looper by Kevin Simback.
When to use: design an agent loop, set up a self-review or LLM-as-judge loop, build a multi-model council, create review-gated iterative workflows, or scaffold a /goal-driven process with typed verification and termination guards.
code-quality-and-reviewSelf-contained port of Lauren Tan's pstack (poteto-mode) — 23 playbooks, 21 procedures, 21 engineering principles. No plugin install, no Cursor required. Runs in Claude Code, Cursor, Kiro, and OpenCode. One orchestrator that reads your task, picks the right playbook (bug fix, feature, refactoring, perf, investigation, prototype, babysit, shipping, autonomous run, orchestrate), routes to bundled procedures (how, why, architect, arena, swarm, interrogate, unslop, tdd), and applies engineering principles with traceable citations.
When to use: any task that needs rigor — nontrivial code changes, architecture decisions, debugging with repro-first discipline, adversarial reviews, PR babysitting and shipping, long autonomous runs — or "poteto-mode", "work like poteto", "pstack". Works single-model; panels degrade to fresh-context passes without weakening any verification gate.
code-quality-and-reviewStrips mechanical writing signals from Brazilian Portuguese text and restores rhythm, precision, and voice. Removes AI slop patterns, restores semantic entropy, and injects voice and personality. The goal is a better text, not a fooled detector: no rewrite can guarantee that a tool will classify the result as human, and the skill treats AI-detector scores as an invalid criterion. Born from the English humanizer skill but evolved into something far more complete — with 55+ patterns specific to PT-BR that no other source has cataloged.
Origin story: I started from the English humanizer skill by @blader (based on Wikipedia's "Signs of AI writing"), researched what makes AI text detectable specifically in Brazilian Portuguese, discovered there was zero consolidated material on PT-BR AI patterns, cataloged 55+ patterns from scratch (including 10 exclusive to Brazilian Portuguese like gerundismo, officialese, and ENEM-style hedging), incorporated the tropes.fyi directory and the concept of semantic ablation (The Register, 2026), and built a skill that doesn't just remove bad patterns — it restores the entropy that AI strips away.
Why it's better for PT-BR than the original:
When to use: humanize PT-BR text, remove AI slop, rewrite with voice, fix generic/bureaucratic tone, review text from another agent, "tirar cara de IA", "dar vida ao texto".
Improvements in v1.2 (Jun 2026):
New in v1.3 (Jul 2026):
references/padroes-portugues-simplificado.md with ~50 lexical substitutions, quantitative metrics from NILC-Metrix (ASL, TTR, syntactic complexity), 15 writing rules in 3 priority levels, and 4 application domains (government, health, tech, education)New in v1.5 (Sep 2026):
references/padroes-consumo-rapido.md with formatting rules, cut rules, TRAVA FACTUAL integration, and verification checklistNew in v1.4 (Aug 2026):
pra, tá, cê), regionalisms (uai, oxe, tchê), mixed feelings, parenthetical self-correction, dated slang, sentence-length variation. The skill must not "fix" these by standardizationmodo_criacao (writing from scratch): the pattern list becomes an output filter rather than a repair pass. Write first, then sweep — starting with the five patterns that account for most slips in new text—, – and -- before delivery, plus explicit exceptions (fiction dialogue, author sample)Credits and sources for humanizar:
The false-positive guard, the human-marks list, the from-scratch writing mode and five patterns were incorporated from PedroLLou/humanizador (MIT), the Brazilian Portuguese version of blader/humanizer (MIT), which in turn derives from Wikipedia: Signs of AI writing, maintained by WikiProject AI Cleanup.
Portuguese-language sources behind those adaptations:
Confidence levels. No single pattern proves artificial origin; the signal is accumulation. These have direct support in published Portuguese sources or in released measurements: AI vocabulary, negative parallelism ("não apenas X, mas Y"), the aparte em-dash, decorative emoji, curly quotes, chatbot leftovers, stacked connectives, English-imported punctuation and fabricated sources. The rest are heuristics, not proof.
The Português Simplificado profile derives its operations from the PorSimples project (NILC/USP) and the techniques associated with Brazil's Lei 15.263/2025 (National Plain Language Policy).
code-quality-and-reviewStrips mechanical writing signals from English text and restores rhythm, precision, and voice. Combines pattern detection (43 patterns across 3 tiers), statistical rhythm measurement (burstiness, TTR, entropy), and voice injection into a single iterative skill. Built on research from the RAID Benchmark (ACL 2024) and NeurIPS 2023. Same positioning as humanizar: the metrics are measurable proxies for natural rhythm, not a scoreboard to beat, and detector scores never decide what gets rewritten.
Origin story: Companion to the PT-BR humanizar skill, but 100% original English work. Synthesizes the best of three open-source humanizer skills: blader/humanizer (10.6K stars, 29 patterns), brandonwise/humanizer (560-term vocab filter, statistical signals), and Aboudjem/humanizer-skill (43 patterns, P31-P43 emerging 2026 discoveries). Goes beyond all three by adding: research-calibrated empirical baselines, iterative scoring with strategy fallback, 7 voice presets, a scripts/measure.py for deterministic metrics, and the critical insight that synonym-swapping changes nothing while structural paraphrasing does — the RAID study measured that as detector accuracy dropping from 70.3% to 4.6%, which is evidence about rhythm and sentence architecture, not a goal in itself.
Why it's different from the existing humanizer skills:
scripts/measure.py — deterministic TTR/burstiness/entropy calculation (zero dependencies)When to use: humanize English text, remove AI slop, de-slop content, make text sound human, add voice, fix bland/generic tone, bypass AI detection, pass GPTZero/Originality.ai, review text from another agent, rewrite naturally.
library-and-api-referenceGenerates, validates, and explains auth.md files — the open protocol that lets AI agents register for services on behalf of users without signup forms. Supports the Agent Verified flow (ID-JAG identity assertions via trusted providers like OpenAI, Anthropic, Cursor) and the User Claimed flow (OTP-based registration with anonymous start or email required entrypoints). Extends RFC 9728 (Protected Resource Metadata) with CIMD support.
When to use: make your app agent-ready by publishing an auth.md, generate Protected Resource Metadata and Authorization Server metadata with agent_auth block, validate an existing auth.md against the protocol spec, implement agent registration endpoints (/agent/auth, /agent/auth/claim, /agent/auth/revoke), understand how the auth.md protocol works, configure ID-JAG verification and trust lists, set up OTP claim ceremonies.
📄 View full documentation | 🌐 auth-md.com
library-and-api-referenceCreate, validate, and enrich Open Knowledge Format bundles — the open spec (v0.1, announced June 12, 2026 by Sam McVeety & Amir Hormati at Google Cloud) that formalizes the "LLM Wiki" pattern into a portable, interoperable format for organizational knowledge. Markdown files with YAML frontmatter, consumable by any AI agent without SDK. Includes bash validator, conversion guides (Notion, Obsidian, CSV), and integration with Google Cloud Knowledge Catalog via kcmd CLI/MCP.
When to use: create OKF bundles, validate conformance, enrich concepts with schema/citations/cross-links, convert existing knowledge (Notion exports, Obsidian vaults, spreadsheets) to OKF, structure a knowledge base for AI agent consumption, generate index.md and log.md files, push bundles to Knowledge Catalog via kcmd.
📄 View full documentation | 🌐 okf.md
This skill has been retired. The original project now offers a more complete skill with 140+ topics, live updates via MCP server, delta re-audits, and MDN pairing — far beyond what we maintained here.
👉 Use the official skill: https://specification.website/.well-known/agent-skills/specification-website/SKILL.md
MCP endpoint:
https://mcp.specification.website/mcp
Migrated → This skill moved to github.com/lgpd-app/skills
Audits websites for compliance with Brazil's LGPD (Lei 13.709/2018).
Migrated → This skill moved to github.com/lgpd-app/skills
Generates and validates lgpd.md files — the LGPD compliance declaration standard.
code-quality-and-reviewEvaluate any agent skill against a merged framework — Anthropic's Claude Code best practices plus Matt Pocock's writing-great-skills methodology — across 4 axes (Trigger, Structure, Steering, Pruning). Produces an evidence-cited scorecard (0–100), a weighted overall score, and diagnosed failure modes with prioritized fixes.
v2.2 — Trigger Eval (empirical): now includes an empirical trigger-testing step inspired by Philipp Schmid's (Google DeepMind) talk "Don't Ship Skills Without Evals". Generates 5 should-trigger + 5 should-not-trigger prompts, runs them via independent sub-agents, and measures whether the skill's description actually causes invocation — bridging the gap between static quality analysis and runtime validation.
When to use: evaluate a skill, rate skill quality, audit SKILL.md, compare two skills, skill scorecard, review best practices compliance, or check if a skill is production-ready.
18 scored criteria across 4 axes: Invocation design · Description quality · Steps vs. reference clarity · Branch-aware disclosure · Conciseness · Coherent scope · Leading words · Completion criteria · Gotchas · Grounded in expertise · Avoids railroading · No-ops · Single source of truth · Relevance & sediment + 4 conditional (Setup flow · Memory · Scripts · Hooks)
5 bonus patterns (measured, not scored): Validation loops · Output templates · Procedures over declarations · Defaults over menus · Trace-checkable steering
How it differs from agentskills.io evals and skill-creator benchmark:
| This skill | agentskills.io evals | skill-creator benchmark | |
|---|---|---|---|
| Evaluates | Skill structure quality + trigger empirically | Skill output quality | Output + regression + obsolescence |
| Method | Static inspection + sub-agent trigger eval | Run test cases + grade | A/B blind comparison + multi-agent |
| When | Is it well-built? Does it trigger correctly? | Does it work? | Did it regress? Still needed? |
| Output | Scorecard + grade A-F + trigger hit/leak rates | pass_rate, tokens, time | benchmark.json + comparator verdict |
| Platform | Any agent | Any agent | Claude Code only (plugin) |
Use in sequence: skill-evaluation (design review + trigger testing) → evals (functional validation) → benchmark (ongoing monitoring).
code-quality-and-reviewObjectively evaluates a UI/web design against the pols.dev anti-slop design law: sweeps an ID'd catalog of slop tells across 6 families (color & light, typography, components, layout, motion, execution), checks 6 absolute execution rules, and scores 8 weighted axes — including a 3x-weighted Signature axis with a hard gate, so a "clean but empty" page can't hide behind restraint. Emits a Slop Report with a 0–100 Slop Index and grade A–F. Every finding follows cite-or-cut: no concrete evidence (hex value, font name, file:line, screenshot region), no tell.
How it evaluates: live URL (browser-automation SOP: dual-viewport full-page captures, interaction pass, zoom crops), static screenshots, code path (grep-led sweep), or Figma export — anything not observable is marked Unverifiable, never guessed. Deterministic scoring via scripts/score.py, with a --fail-below CI gate for blocking PRs on preview-deploy design quality.
When to use: evaluate design slop, generate a slop report, check if a design looks AI-generated or generic, audit a landing page design, de-slop review, compare two designs (before/after), track design evolution over time.
New in v1.1.0 (Aug 2026):
// BRIEF:, // DESIGN DECISION:, // CONTEXT:, // PREMIUM PAIR: tags for documenting excluded tells with audit trailCompanions: method inspired by skill-evaluation; for text (not design), human-ai and humanizar do the de-slopping.
runbooksFull-stack application security agent — performs SAST (static code analysis), DAST (dynamic testing against running apps), threat modeling, vulnerability triage, remediation, and penetration testing. Combines source code review with live testing against local dev servers or production targets for complete evidence correlation.
When to use: security scan a repository, review a PR for security issues, build a threat model, triage vulnerability findings, fix a security bug, pentest a web application, validate a security fix, track findings to GitHub/Jira/Linear, generate a security report.
Key features:
validate-findings.cjs) for CI integrationArchitecture:
security-specialist/
├── SKILL.md (router + core principles + anti-patterns)
├── steering/ (12 workflow docs including hunting methodology)
├── scripts/ (5 tools: Python + Node.js validator)
└── references/ (5 spec docs: finding format, report format, severity policy, artifacts, report-schema.json)
Improvements in v2.0 (Jun 2026):
steering/hunting.md with 9 attack classes and 12-angle hunting methodologyreferences/report-schema.json for structured findings with trace, conditions, execution, confidencescripts/validate-findings.cjs zero-dependency JSON schema validatorci-cd-and-deploymentComprehensive skill for building, migrating, and maintaining Astro v7 projects. Covers the full lifecycle: best practices, v6→v7 migration with structured plan, validation of breaking/deprecated patterns, AI-enhanced dev server (background mode, JSON logging), advanced routing with src/fetch.ts, route caching, Sätteri Markdown, Rust compiler, Starlight docs, Pagefind search, SEO, testing, and deployment to 8+ platforms including Coolify.
When to use: build Astro sites, upgrade to v7, deploy on Coolify/Vercel/Netlify/Cloudflare, validate breaking changes, configure Starlight docs, set up Pagefind search, use background dev server as AI agent, configure route caching.
Key features:
product-verificationAudits, scores, and compares repositories containing portable Agent Plugins against the official Agent Plugins specification. Produces an evidence-cited 0–100 scorecard with conformance gate (PASS/PARTIAL/FAIL), identifies release blockers, and compares two plugins side by side. Works with any agent client — evaluates portable conformance, not client-specific features.
When to use: audit a plugin repo, check plugin.json or mcp.json conformance, validate bundled Agent Skills, assess MCP server configurations, produce a plugin scorecard, identify release blockers, compare two agent plugins.
Key features:
scripts/score.pyrunbooksPlaybook of 101 evidence-backed principles for designing SaaS and startup products that convert, retain, and monetize — landing pages & CRO, onboarding/activation, churn reduction, pricing psychology, behavioral science, feature discipline, positioning/ICP, go-to-market, and AI-era differentiation. Every principle names its mechanism (decoy effect, Zeigarnik, Schwartz awareness levels…) and links back to its source post. Ships with revenue-math scripts (A/B sample size, churn→LTV, CAC per closed deal), an audit output template, per-project memory (rcd-log.md), and license-enforcing guardrail hooks.
Origin story: Richard (@richardrx, "Design for startups" — ex-Volkswagen, PayPal, IBM) published these principles as 101 posts in Portuguese on X. Helio Costa obtained the author's permission, extracted the posts via the X API, translated them to English, and distilled them into the original skill (heliocosta-dev/revenue-centric-design). This repository hosts an evolved derivative of that work.
Evolution measured with skill-evaluation: the as-downloaded skill scored 60/100 (B, borderline C); one improvement pass later, 73/100 (B):
| Criterion | before | after |
|---|---|---|
| Scripts & libraries | 0 | 75 |
| Gotchas section | 35 | 88 |
| Coherent scope | 55 | 72 |
| Progressive disclosure | 78 | 90 |
| Description for trigger | 78 | 90 |
| Repo footprint | 39 MB | 176 KB |
After the compared run, the skill also gained the audit template, the project log, full license compliance, and hook-based guardrails — each closing a finding the scorecard had prioritized. This is exactly the loop skill-evaluation was built for: evaluate → fix the top findings → re-evaluate → compare.
When to use: improve conversion on a landing page, fix activation/onboarding, reduce churn, design pricing tables and upgrade paths, sharpen ICP/positioning, apply behavioral-science mechanisms, sanity-check A/B tests, differentiate in the AI era.
⚠️ License: source-available, not Apache 2.0 — attribution to @richardrx required, and gambling/betting/casino use is prohibited (enforced at runtime by bundled hooks). See the skill's LICENSE.
Skills revised in March 2026 following the Anthropic standard for Agent Skills structure and quality. Source: Improving Skill Creator: Test, Measure and Refine Agent Skills
You can install these skills using any compatible installer or manually. Below are the most popular options.
npx skills add https://github.com/fabricioctelles/skills
Or install a specific skill:
npx skills add https://github.com/fabricioctelles/skills -s startup-idea
npx skills add https://github.com/fabricioctelles/skills -s revenue-centric-design
npx skills add https://github.com/fabricioctelles/skills -s geo-optimization
npx skills add https://github.com/fabricioctelles/skills -s substack-expert
npx skills add https://github.com/fabricioctelles/skills -s humanizar
npx skills add https://github.com/fabricioctelles/skills -s human-ai
npx skills add https://github.com/fabricioctelles/skills -s pier-cloud
npx skills add https://github.com/fabricioctelles/skills -s coolify-operator
npx skills add https://github.com/fabricioctelles/skills -s astro-sites-manager
npx skills add https://github.com/fabricioctelles/skills -s security-specialist
npx skills add https://github.com/fabricioctelles/skills -s ultimate-design-system-master
npx skills add https://github.com/fabricioctelles/skills -s design-md-validator
npx skills add https://github.com/fabricioctelles/skills -s skill-evaluation
npx skills add https://github.com/fabricioctelles/skills -s slop-eval
npx skills add https://github.com/fabricioctelles/skills -s agent-plugin-eval
npx skills add https://github.com/fabricioctelles/skills -s agent-ready-cloudflare
npx skills add https://github.com/fabricioctelles/skills -s auth-md
npx skills add https://github.com/fabricioctelles/skills -s pstack-skill
npx skills add https://github.com/fabricioctelles/skills -s okf-open-knowledge-format
npx skills add https://github.com/fabricioctelles/skills -s ralph-loop-kiro-specs
npx skills add https://github.com/fabricioctelles/skills -s loop-architect
npx skills add https://github.com/fabricioctelles/skills -s resume-ats-beater
A package manager for skills with cross-agent translation. Runs with zero install:
npx skillkit add fabricioctelles/skills
Or install the CLI globally:
npm install -g skillkit # full
npm install -g skillkit --omit=optional # slim, ~75% smaller, no native addons
skillkit install fabricioctelles/skills
Target specific agents (46 supported, including Claude Code, Cursor, Codex, Gemini CLI, Windsurf, Copilot, OpenCode, Kiro):
skillkit install fabricioctelles/skills --agent claude-code,cursor
Cross-agent translation — rewrites a skill into another agent's format:
skillkit translate humanizar --to cursor
skillkit translate --all --to windsurf,codex
skillkit translate slop-eval --to copilot --dry-run
skillkit recommend suggests skills based on your project's stack, and skillkit ui opens an interactive TUI.
npm install -g agent-skills-cli
Then install the skills:
skills add https://github.com/fabricioctelles/skills
Or use without global install:
npx agent-skills-cli install https://github.com/fabricioctelles/skills
git clone https://github.com/fabricioctelles/skills.git
# Example for Cursor
cp -r skills/geo-optimization .cursor/skills/
cp -r skills/substack-expert .cursor/skills/
cp -r skills/pier-cloud .cursor/skills/
cp -r skills/ultimate-design-system-master .cursor/skills/
cp -r skills/resume-ats-beater .cursor/skills/
cp -r skills/coolify-operator .cursor/skills/
cp -r skills/agent-ready-cloudflare .cursor/skills/
cp -r skills/ralph-loop-kiro-specs .cursor/skills/
cp -r skills/loop-architect .cursor/skills/
cp -r skills/humanizar .cursor/skills/
cp -r skills/auth-md .cursor/skills/
cp -r skills/astro-sites-manager .cursor/skills/
cp -r skills/agent-plugin-eval .cursor/skills/
# Example for Claude Code
cp -r skills/geo-optimization .claude/skills/
cp -r skills/substack-expert .claude/skills/
cp -r skills/pier-cloud .claude/skills/
cp -r skills/ultimate-design-system-master .claude/skills/
cp -r skills/resume-ats-beater .claude/skills/
cp -r skills/coolify-operator .claude/skills/
cp -r skills/agent-ready-cloudflare .claude/skills/
cp -r skills/ralph-loop-kiro-specs .claude/skills/
cp -r skills/loop-architect .claude/skills/
cp -r skills/humanizar .claude/skills/
cp -r skills/auth-md .claude/skills/
cp -r skills/astro-sites-manager .claude/skills/
cp -r skills/agent-plugin-eval .claude/skills/
# Example for Kiro
cp -r skills/geo-optimization .kiro/skills/
cp -r skills/substack-expert .kiro/skills/
cp -r skills/pier-cloud .kiro/skills/
cp -r skills/ultimate-design-system-master .kiro/skills/
cp -r skills/resume-ats-beater .kiro/skills/
cp -r skills/coolify-operator .kiro/skills/
cp -r skills/agent-ready-cloudflare .kiro/skills/
cp -r skills/ralph-loop-kiro-specs .kiro/skills/
cp -r skills/loop-architect .kiro/skills/
cp -r skills/humanizar .kiro/skills/
cp -r skills/auth-md .kiro/skills/
cp -r skills/astro-sites-manager .kiro/skills/
cp -r skills/agent-plugin-eval .kiro/skills/
The Agent Skills format is universal and works with any compatible agent. See the official specification for details.
skills/
├── startup-idea/
│ ├── SKILL.md
│ └── evals/ # 3 lenses: Graham, Koe, Godin
├── revenue-centric-design/
│ ├── SKILL.md
│ ├── references/ # 101 principles + audit output template
│ └── scripts/ # revenue math: A/B sample size, churn to LTV, CAC
├── geo-optimization/
│ ├── SKILL.md
│ └── references/ # guiding principles and case studies
├── substack-expert/
│ ├── SKILL.md
│ └── references/ # formatting best practices, SEO output example
├── humanizar/
│ ├── SKILL.md
│ └── references/ # 55+ AI patterns specific to Brazilian Portuguese (7 files)
├── human-ai/
│ ├── SKILL.md
│ ├── references/ # 43 EN patterns, empirical baselines
│ └── scripts/ # measure.py — deterministic metrics
├── pier-cloud/
│ ├── SKILL.md
│ ├── scripts/ # Python scripts for API consumption
│ └── references/ # API reference, troubleshooting guide
├── coolify-operator/
│ ├── SKILL.md
│ └── evals/ # 8 test scenarios
├── astro-sites-manager/
│ ├── SKILL.md
│ └── references/ # Astro v7 migration, routing, deploy targets
├── security-specialist/
│ ├── SKILL.md
│ ├── steering/ # 12 workflow docs including hunting methodology
│ ├── scripts/ # 5 tools: Python + Node.js validator
│ └── references/ # 5 spec docs: finding/report format, severity policy
├── ultimate-design-system-master/
│ ├── SKILL.md
│ └── references/ # briefing questionnaire, 10 specialized prompt files
├── design-md-validator/
│ ├── SKILL.md
│ └── references/ # Google DESIGN.md spec, lint rules, export formats
├── skill-evaluation/
│ ├── SKILL.md
│ ├── references/ # 18 criteria across 4 axes, scorecard template
│ └── scripts/ # trigger eval runner
├── slop-eval/
│ ├── SKILL.md
│ ├── references/ # 8 axes of the anti-slop law
│ └── scripts/ # Slop Index calculator
├── agent-plugin-eval/
│ ├── SKILL.md
│ ├── agents/ # default evaluation agent
│ ├── references/ # spec checklist, 18-criterion rubric, output template
│ └── scripts/ # score.py + inspect_plugin.py (static audit)
├── agent-ready-cloudflare/
│ ├── README.md # human-readable documentation with examples
│ ├── SKILL.md # main skill (API docs, operational flow, prompt templates)
│ └── */SKILL.md # 20 implementation sub-skills (robots-txt, mcp-server-card, etc.)
├── auth-md/
│ ├── SKILL.md
│ └── references/ # protocol template, validation rules, metadata schema, example, implementation guide
├── pstack-skill/
│ ├── README.md # human-readable guide: install, use cases, model roles
│ ├── SKILL.md # the orchestrator (playbook router, principles index, autonomy rules)
│ ├── UPSTREAM_COMMIT # reviewed upstream reference
│ ├── playbooks/ # 23 step-by-step workflows copied verbatim onto todolists
│ ├── references/ # 21 principles, 21 bundled procedures, plan + bot-review triage
│ └── scripts/ # decision-log helper, worktree audit
├── okf-open-knowledge-format/
│ ├── SKILL.md
│ ├── references/ # OKF spec, bundle anatomy, enrichment rules
│ └── scripts/ # validate.sh — bundle validator
├── ralph-loop-kiro-specs/
│ ├── SKILL.md
│ ├── scripts/ # bash loop runner script
│ └── references/ # Ralph agent prompt template
├── loop-architect/
│ ├── SKILL.md # loop design coach (adapted from Looper by ksimback)
│ ├── scripts/ # compiler and model detection
│ ├── templates/ # portable Python runner
│ ├── references/ # rubrics (goal, verification, council, control)
│ ├── schemas/ # loop.yaml JSON schema
│ └── examples/ # ai-workflow-mapping example
└── resume-ats-beater/
├── SKILL.md
└── references/ # diagnostic templates, output structure
Created by ft.ia.br
Apache 2.0 — see LICENSE for details — except where a skill directory contains its own LICENSE file, which governs that skill instead.
⚠️ Exception: skills/revenue-centric-design/ is source-available, not open-source. The underlying ideas are the intellectual property of Richard (@richardrx), used with permission, and may not be used for gambling, betting, or casino products. That restriction survives any copy or derivative and is not waived by this repository's Apache 2.0 license.
name: pstack-skill
description: >
Rigorous engineering orchestrator ported from Lauren Tan's pstack
(poteto-mode): reads your task, picks one of 23 playbooks (bug fix,
feature, refactoring, perf, investigation, prototype, babysit, shipping,
autonomous run, orchestrate, and more), routes to bundled procedures
(how, why, architect, arena, swarm, interrogate, unslop, technical-writing,
show-me-your-work, tdd, and others), and applies 23 engineering principles.
Self-contained: no plugin install, no sibling skills required, works with
any agent that reads skills.sh-format SKILL.md files. Use whenever a task
needs rigor: nontrivial code changes, architecture decisions, debugging,
reviews, PRs, long autonomous runs, or "work like poteto", "poteto-mode",
"pstack".
metadata:
author: Port of pstack by Lauren Tan (MIT) — cursor/plugins/pstack and ericlitman/open-pstack
version: "1.0"
date: 2026-08-24
source: https://github.com/cursor/plugins/tree/main/pstackAn orchestrator for high-rigor engineering work, distilled from Lauren Tan's pstack plugin into one self-contained skill. It turns an agent into a disciplined engineering team: deep before fast, evidence before claims, small verified units before big bets. The goal is less, higher-quality code.
This skill is sticky. Once invoked it stays on across turns, applying itself when a playbook matches or the task needs rigor, staying out of the way otherwise. Opt out any time by saying so.
Everything referenced here ships inside this skill:
playbooks/*.md — the step-by-step workflows. Copy matched steps verbatim.references/principles.md — the full text of the 23 principles indexed below.references/bugbot-triage.md — bot-review triage.references/skills/*.md — bundled procedures named by bold lowercase words (how, why, architect, arena, swarm, interrogate, unslop, no-comments, technical-writing, show-me-your-work, figure-it-out, tdd, blast-radius, recall, reflect, teach, bro, typescript-best-practices, create-verification-skill, maintain-verification-skill, setup-pstack). Read the file when a step routes to one.scripts/log.sh — decision-log helper. scripts/worktree-audit.sh — disk reclaim audit.scripts/check-plan.mjs — validates the multi-phase plan checklist.scripts/check-upstream.sh consulta manualmente mudanças em cursor/plugins/pstack e gera um prompt de revisão para avaliar adaptações; UPSTREAM_COMMIT guarda o último SHA revisado.Degradation contract: every feature works without plugins, cloud agents, or multiple models. Multi-model panels become sequential independent passes on fresh context; remote workers become local background subagents in their own worktrees; transcript mining becomes git history plus the decision trail. Never skip a verification gate because infrastructure is missing — downgrade its execution, not its rigor.
Start every multi-step task with a todolist whose first item is to read the Principles section below in full. The principles ground every trigger here. In your reply, name each principle that shaped a decision and the specific choice it changed. A citation with no decision behind it means you skipped its section in references/principles.md; it must trace to a real choice the principle drove.
Remaining triggers:
references/bugbot-triage.md, dismissing noise with a concrete reason instead of churning code.Read the full rule in references/principles.md for any principle you apply. Each entry names when it applies.
Core
Architecture
Verification
Delegation
Meta
Just do it. Use available tools freely. Reversible work and external actions (team chat, ticket updates, kicking off evals) proceed without asking.
Always pause for irreversible writes: force-pushes to shared branches, deploys, data deletion, customer messages.
Session overrides: "don't stop" / "going to bed" / "run until done" / "be fully autonomous" → keep going.
No is an acceptable answer. Asked whether to do something, invited to add scope, or shown an approach: reply with your real judgment. Decline, push back, or say "this doesn't earn its place" when true. A recommendation is a judgment, not a validation. Agreement is not the default; candor over sycophancy.
Spawn general-purpose subagents (your platform's Task/subagent mechanism) for delegated steps; brief each with its exact scope, the named data shape, success criteria, and the report format expected back. Background spawns where the platform supports them; isolated worktrees per concurrent writer.
Model roles resolve per references/skills/setup-pstack.md: worker (mechanical edits, explorers, swarm), builder (precisely specified implementation), judge (reasoning, prose, synthesis, lead review), peer (second opinion from a different family than judge). Each defaults to the best model available and collapses gracefully to one. Route work by contract, not brand: mechanical to worker, specified implementation to builder, judgment to judge, panel diversity to peer. Configure bindings once via setup; runtime never pauses to ask.
You own every subagent's work. Review the diff and write your own summary; never pass through what it said. Interrupt-chained resumes silently drop directives, so fire a fresh subagent with consolidated scope rather than trusting a "done" summary. A second opinion is the same prompt against a different model or a fresh context; agreement is high-signal.
Write the reply clean as you draft it. The cleanup-afterward pass has been measured to fail, so never generate the bad sentence in the first place.
main.js owns persistence and the IPC handlers"). A bold section header joined to its text by a dash. Write the header as its own sentence ("Verification. End to end via CDP").Every playbook ends with a reply written this way, PR link included when one exists. The per-playbook reply lines name only content unique to that playbook.
Comments follow the same rule as the reply. Write them clean as you go; a flat "no narrating comments" ban does not catch them, because you have to not write them in the first place. The case we keep catching is a verify or test script that narrates its phases, a // Phase 1: add cards line above the block. Delete it; the assertion or log string is the only doc you need. Write assert(ok, 'persisted across restart'), not a comment plus the code. This applies to every file you produce, including delegates' diffs and verify scripts. Keep a comment only for a non-obvious why the code cannot show.
Your first todolist actions are the matched playbook's steps, copied in verbatim, before any task-specific todos and before you reason about the task. The failure mode is reading a playbook then writing a bespoke plan that drops its named steps (architect, the throughput checkpoint). A step you choose not to do stays in the list with a one-line skip: <reason>; skipping silently is not allowed. Match the task to a playbook below, open its file, copy its steps verbatim.
A large or cross-cutting effort (a migration across many call sites, an ambitious multi-part change), or work the user steps away from to trust later, routes to the figure-it-out procedure even when a narrower playbook like Feature fits. A standing program-scale project (multi-day, many stacked PRs, fleets of subagents under one coordinator) routes to Orchestrate instead; figure-it-out designs one bespoke run, Orchestrate runs the program.
playbooks/investigation.md.playbooks/bug-fix.md.playbooks/perf-issue.md.playbooks/hillclimb.md.playbooks/runtime-forensics.md.playbooks/trace-forensics.md.playbooks/feature.md.playbooks/refactoring.md.playbooks/prototype.md.playbooks/visual-parity.md.playbooks/authoring-a-skill.md.playbooks/eval.md.playbooks/babysit.md.playbooks/shipping.md.playbooks/autonomous-run.md.playbooks/orchestrate.md.playbooks/autopilot-full.md.playbooks/autopilot-stack.md.playbooks/session-pickup.md.playbooks/pause-safely.md.playbooks/multi-phase-plan.md.playbooks/worktree-cleanup.md.playbooks/opening-a-pr.md.Ported from pstack by Lauren Tan and informed by open-pstack, both MIT. This bundle adapts Cursor-specific mechanics (plugins, cloud agents, Graphite, /loop, bundled scripts) to platform-agnostic equivalents while preserving the operating method.
评论 (0)
暂无评论,成为第一个评论者吧!