[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72YDSB1HYM9CSBE1BDESA65":3,"skill-same:01M72YDSB1HYM9CSBE1BDESA65":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M72YDSB1HYM9CSBE1BDESA65","ruff",null,"Guide for using ruff, the extremely fast Python linter and formatter. Use this when linting, formatting, or fixing Python code.","marcioaltoe\u002Fskills","marcioaltoe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1562865?v=4","01M72Y3750J2CG00P0H2AHDRSZ","Marcio Altoé","01M72Y37642F46H36R4E4S7BNA",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F05-implementation-loop\u002Fruff\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F05-implementation-loop\u002Fruff\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: ruff\ndescription:\n  Guide for using ruff, the extremely fast Python linter and formatter. Use this\n  when linting, formatting, or fixing Python code.\n---\n\n# ruff\n\nRuff is an extremely fast Python linter and code formatter. It replaces Flake8,\nisort, Black, pyupgrade, autoflake, and dozens of other tools.\n\n## When to use ruff\n\n**Always use ruff for Python linting and formatting**, especially if you see:\n\n- `[tool.ruff]` section in `pyproject.toml`\n- A `ruff.toml` or `.ruff.toml` configuration file\n\nHowever, avoid making unnecessary changes:\n\n- **Don't format unformatted code** - If `ruff format --diff` shows changes\n  throughout an entire file, the project likely isn't using ruff for formatting.\n  Skip formatting to avoid obscuring actual changes.\n- **Scope fixes to code being edited** - Use `ruff check --diff` to see fixes\n  relevant to the code you're changing. Only apply fixes to files you're\n  modifying unless the user explicitly asks for broader fixes.\n\n## How to invoke ruff\n\n- `uv run ruff ...` - Use when ruff is in the project's dependencies to ensure\n  you use the pinned version\n- `uvx ruff ...` - Use when ruff is not a project dependency, or for quick\n  one-off checks\n- `ruff ...` - Use if ruff is installed globally\n\n## Commands\n\n### Linting\n\n```bash\nruff check .                  # Check all files in current directory\nruff check path\u002Fto\u002Ffile.py    # Check specific file\nruff check --fix .            # Auto-fix fixable violations\nruff check --fix --unsafe-fixes .  # Include unsafe fixes (review changes!)\nruff check --watch .          # Watch for changes and re-lint\nruff check --select E,F .     # Only check specific rules\nruff check --ignore E501 .    # Ignore specific rules\nruff rule E501                # Explain a specific rule\nruff linter                   # List available linters\n```\n\n### Formatting\n\n```bash\nruff format .                 # Format all files\nruff format path\u002Fto\u002Ffile.py   # Format specific file\nruff format --check .         # Check if files are formatted (no changes)\nruff format --diff .          # Show formatting diff without applying\n```\n\n`uv format` runs the Ruff formatter. Use `uv format --check -- path\u002Fto\u002Ffile.py`\nto check one file. By default, `uv format` selects a Ruff version independently\nof the project's lockfile. When the project pins Ruff, use `uv run ruff format`\nto match its formatter version.\n\n## Configuration\n\nRuff is configured in `pyproject.toml` or `ruff.toml`:\n\n```toml\n# pyproject.toml\n[tool.ruff.lint]\nextend-select = [\"I\", \"UP\"]  # Add import sorting and pyupgrade to the defaults\n\n[tool.ruff.lint.isort]\nknown-first-party = [\"myproject\"]\n```\n\n## Migrating from other tools\n\n### Black → ruff format\n\n```bash\nblack .                       → ruff format .\nblack --check .               → ruff format --check .\nblack --diff .                → ruff format --diff .\n```\n\n### Flake8 → ruff check\n\n```bash\nflake8 .                      → ruff check .\nflake8 --select E,F .         → ruff check --select E,F .\nflake8 --ignore E501 .        → ruff check --ignore E501 .\n```\n\n### isort → ruff check\n\n```bash\nisort .                       → ruff check --select I --fix .\nisort --check .               → ruff check --select I .\nisort --diff .                → ruff check --select I --diff .\n```\n\n## Common patterns\n\n### Apply lint fixes before formatting\n\nRun `ruff check --fix` before `ruff format`. Lint fixes can change code\nstructure (e.g., reordering imports), which formatting then cleans up.\n\n```bash\nruff check --fix .\nruff format .\n```\n\n### Applying and reviewing unsafe fixes\n\nRuff's full diagnostic output can show a suggested change even when `--fix`\nwould leave the code alone. Safe fixes can be applied with `--fix`. Unsafe fixes\nmay change behavior and also require `--unsafe-fixes`. A suggestion marked for\nmanual review, such as removing commented-out code for `ERA001`, requires a\nmanual edit.\n\n```bash\nruff check --fix --unsafe-fixes --diff .  # Preview changes first\nruff check --fix --unsafe-fixes .         # Apply changes\n```\n\n**Always review changes before applying `--unsafe-fixes`:**\n\n- Use `ruff rule \u003CCODE>` to understand why the fix is considered unsafe\n- Verify the fix doesn't violate those assumptions in your code\n\n## Documentation\n\nFor detailed information, read the official documentation:\n\n- https:\u002F\u002Fdocs.astral.sh\u002Fruff\u002F\n","# ruff\n\nRuff is an extremely fast Python linter and code formatter. It replaces Flake8,\nisort, Black, pyupgrade, autoflake, and dozens of other tools.\n\n## When to use ruff\n\n**Always use ruff for Python linting and formatting**, especially if you see:\n\n- `[tool.ruff]` section in `pyproject.toml`\n- A `ruff.toml` or `.ruff.toml` configuration file\n\nHowever, avoid making unnecessary changes:\n\n- **Don't format unformatted code** - If `ruff format --diff` shows changes\n  throughout an entire file, the project likely isn't using ruff for formatting.\n  Skip formatting to avoid obscuring actual changes.\n- **Scope fixes to code being edited** - Use `ruff check --diff` to see fixes\n  relevant to the code you're changing. Only apply fixes to files you're\n  modifying unless the user explicitly asks for broader fixes.\n\n## How to invoke ruff\n\n- `uv run ruff ...` - Use when ruff is in the project's dependencies to ensure\n  you use the pinned version\n- `uvx ruff ...` - Use when ruff is not a project dependency, or for quick\n  one-off checks\n- `ruff ...` - Use if ruff is installed globally\n\n## Commands\n\n### Linting\n\n```bash\nruff check .                  # Check all files in current directory\nruff check path\u002Fto\u002Ffile.py    # Check specific file\nruff check --fix .            # Auto-fix fixable violations\nruff check --fix --unsafe-fixes .  # Include unsafe fixes (review changes!)\nruff check --watch .          # Watch for changes and re-lint\nruff check --select E,F .     # Only check specific rules\nruff check --ignore E501 .    # Ignore specific rules\nruff rule E501                # Explain a specific rule\nruff linter                   # List available linters\n```\n\n### Formatting\n\n```bash\nruff format .                 # Format all files\nruff format path\u002Fto\u002Ffile.py   # Format specific file\nruff format --check .         # Check if files are formatted (no changes)\nruff format --diff .          # Show formatting diff without applying\n```\n\n`uv format` runs the Ruff formatter. Use `uv format --check -- path\u002Fto\u002Ffile.py`\nto check one file. By default, `uv format` selects a Ruff version independently\nof the project's lockfile. When the project pins Ruff, use `uv run ruff format`\nto match its formatter version.\n\n## Configuration\n\nRuff is configured in `pyproject.toml` or `ruff.toml`:\n\n```toml\n# pyproject.toml\n[tool.ruff.lint]\nextend-select = [\"I\", \"UP\"]  # Add import sorting and pyupgrade to the defaults\n\n[tool.ruff.lint.isort]\nknown-first-party = [\"myproject\"]\n```\n\n## Migrating from other tools\n\n### Black → ruff format\n\n```bash\nblack .                       → ruff format .\nblack --check .               → ruff format --check .\nblack --diff .                → ruff format --diff .\n```\n\n### Flake8 → ruff check\n\n```bash\nflake8 .                      → ruff check .\nflake8 --select E,F .         → ruff check --select E,F .\nflake8 --ignore E501 .        → ruff check --ignore E501 .\n```\n\n### isort → ruff check\n\n```bash\nisort .                       → ruff check --select I --fix .\nisort --check .               → ruff check --select I .\nisort --diff .                → ruff check --select I --diff .\n```\n\n## Common patterns\n\n### Apply lint fixes before formatting\n\nRun `ruff check --fix` before `ruff format`. Lint fixes can change code\nstructure (e.g., reordering imports), which formatting then cleans up.\n\n```bash\nruff check --fix .\nruff format .\n```\n\n### Applying and reviewing unsafe fixes\n\nRuff's full diagnostic output can show a suggested change even when `--fix`\nwould leave the code alone. Safe fixes can be applied with `--fix`. Unsafe fixes\nmay change behavior and also require `--unsafe-fixes`. A suggestion marked for\nmanual review, such as removing commented-out code for `ERA001`, requires a\nmanual edit.\n\n```bash\nruff check --fix --unsafe-fixes --diff .  # Preview changes first\nruff check --fix --unsafe-fixes .         # Apply changes\n```\n\n**Always review changes before applying `--unsafe-fixes`:**\n\n- Use `ruff rule \u003CCODE>` to understand why the fix is considered unsafe\n- Verify the fix doesn't violate those assumptions in your code\n\n## Documentation\n\nFor detailed information, read the official documentation:\n\n- https:\u002F\u002Fdocs.astral.sh\u002Fruff\u002F\n",{"name":5,"description":7},"main","dea450cfd9df78b5cf721964ef178a75cea55cbb","skills\u002F05-implementation-loop\u002Fruff",2,"https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills","https:\u002F\u002Fmarcioaltoe.github.io\u002Fskills\u002F","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe","Senior Software Engineer · Backend, Systems & AI","2026-11-14 18:29:56",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add marcioaltoe\u002Fskills --skill ruff",{"tool":40,"command":41},"bunx","bunx skills add marcioaltoe\u002Fskills --skill ruff",{"tool":43,"command":44},"pnpm","pnpm dlx skills add marcioaltoe\u002Fskills --skill ruff","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F05-implementation-loop\u002Fruff\u002FSKILL.md",true,[48],{"path":49,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":16},"LICENSE","许可证",1077,[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":20},"01M72YNVSF4JTTQG3YTR9QNT4Z","startup-validator","Comprehensive startup idea validation and market analysis tool. Use when users need to evaluate a startup idea, assess market fit, analyze competition, validate problem-solution fit, or determine market positioning. Triggers include requests to \"validate my startup idea\", \"analyze market opportunity\", \"check if there's demand for\", \"research competition for\", \"evaluate business idea\", or \"see if my idea is viable\". Provides data-driven analysis using web search, market frameworks, competitive research, and positioning recommendations.","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F10-marketing\u002Fstartup-validator\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":20},"01M72YNN34B4MYKEX1X6BB1NS1","positioning-icp","When the user wants to define their ideal customer profile, position an AI product, build messaging architecture, or validate product-market fit. Also use when the user mentions 'ICP,' 'ideal customer profile,' 'positioning,' 'PMF,' 'product-market fit,' 'messaging,' 'buyer persona,' 'enrichment signals,' 'market positioning,' or 'competitive positioning.' This skill covers market positioning, ICP definition, messaging architecture, and PMF validation for AI-native products. Do NOT use for technical implementation, code review, or software architecture.","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F10-marketing\u002Fpositioning-icp\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":20},"01M72YNG8XJ4RHRB5DQMCY9C1N","copywriting","When the user wants to write or rewrite page copy (homepage, landing, pricing, feature), or asks which headline, promise, or message to lead with. Diagnoses the input first (blank brief, real voice, or point edit) and changes only what it calls for. Claims must be supportable; a declined claim names the evidence that would unlock it. No AI tells like 'it's not X, it's Y' or 'no X, no Y, no Z'. For editing, see copy-editing. For emails, see emails. For the offer, see offers.","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F10-marketing\u002Fcopywriting\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":20},"01M72YNBF4JMQ4VCFHTW0WS6SD","business-storyteller","Transforms technical work into persuasive business-language documents for non-technical stakeholders, including internal announcements, approval proposals, incident explainers, technical-debt cases, product explainers, and investor or partner memos. Use when the user asks to present technical work to the company, explain software to business teams, write a business case, make an approval document, or convert a technical artifact into stakeholder communication in the requested language. Do not use for READMEs, specs, ADRs, external marketing pages, or customer-facing sales copy.","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F10-marketing\u002Fbusiness-storyteller\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":20},"01M72YN8NQ6QR0GHX2A8YW2K4T","brand-storytelling","Help users craft compelling brand narratives. Use when someone is defining brand strategy, writing company positioning, creating pitch narratives, developing messaging frameworks, or trying to make their company story more memorable.","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F10-marketing\u002Fbrand-storytelling\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":92,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":20},"01M72YN3CJH7CKPF4AXNY79Q9S","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F09-learning-loop\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmarcioaltoe\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002F09-learning-loop\u002Fskill-creator\u002FSKILL.md",[],[]]