[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CV8KRS3NSSHQ19X1ACFEB7":3,"skill-same:01M7CV8KRS3NSSHQ19X1ACFEB7":48},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CV8KRS3NSSHQ19X1ACFEB7","cisco-ios-patterns",null,"Cisco IOS and IOS-XE review patterns for show commands, config hierarchy, wildcard masks, ACL placement, interface hygiene, and safe change-window verification.","Henrique1601\u002FSkiilsToIAs","Henrique1601","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92006691?v=4","01M7CRXVT0GVXVK80JT1GR687S","Henrique Bezerra Dos Santos","01M7CRXVTN5Y8TMWJ1MDSKCQ1T",0,"MIT","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fdevops-cloud\u002Fcisco-ios-patterns\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cisco-ios-patterns\ndescription: Cisco IOS and IOS-XE review patterns for show commands, config hierarchy, wildcard masks, ACL placement, interface hygiene, and safe change-window verification.\nmetadata:\n  origin: community\n---\n\n# Cisco IOS Patterns\n\nUse this skill when reviewing Cisco IOS or IOS-XE snippets, building a\nchange-window checklist, or explaining how to collect evidence from a router or\nswitch without making the incident worse.\n\n## When to Use\n\n- Reviewing IOS or IOS-XE configuration before a planned change.\n- Choosing read-only `show` commands for troubleshooting.\n- Checking ACL wildcard masks and interface direction.\n- Explaining global, interface, routing process, and line configuration modes.\n- Verifying that a change landed in running config and was saved intentionally.\n\n## Operating Rules\n\nTreat IOS examples as patterns, not paste-ready production changes. Confirm the\nplatform, interface names, current config, rollback path, and out-of-band access\nbefore making changes on a real device.\n\nPrefer this workflow:\n\n1. Capture current state with read-only commands.\n2. Review the exact candidate config.\n3. Confirm management access cannot be locked out.\n4. Apply the smallest change in a maintenance window.\n5. Re-read state, compare to the baseline, then save only after validation.\n\n## Mode Reference\n\n```text\nRouter> enable\nRouter# show running-config\nRouter# configure terminal\nRouter(config)# interface GigabitEthernet0\u002F1\nRouter(config-if)# description UPLINK-TO-CORE\nRouter(config-if)# no shutdown\nRouter(config-if)# exit\nRouter(config)# end\nRouter# show running-config interface GigabitEthernet0\u002F1\n```\n\n`running-config` is active memory. `startup-config` is what survives reload.\nDo not save a change just because a command was accepted; validate behavior\nfirst, then use `copy running-config startup-config` if the change is approved.\n\n## Read-Only Collection\n\n```text\nshow version\nshow inventory\nshow processes cpu sorted\nshow memory statistics\nshow logging\nshow running-config | section line vty\nshow running-config | section interface\nshow running-config | section router bgp\nshow ip interface brief\nshow interfaces\nshow interfaces status\nshow vlan brief\nshow mac address-table\nshow spanning-tree\nshow ip route\nshow ip protocols\nshow ip access-lists\nshow route-map\nshow ip prefix-list\n```\n\nCollect the specific section you need instead of dumping full config into a\nticket when the config may contain secrets, customer names, or private topology.\n\n## Wildcard Masks\n\nIOS ACL and many routing statements use wildcard masks, not subnet masks.\n\n```text\nSubnet mask       Wildcard mask\n255.255.255.255   0.0.0.0\n255.255.255.252   0.0.0.3\n255.255.255.0     0.0.0.255\n255.255.0.0       0.0.255.255\n```\n\nReview wildcard masks before deployment. A subnet mask accidentally used as a\nwildcard can match far more traffic than intended.\n\n```text\nip access-list extended WEB-IN\n  10 permit tcp 192.0.2.0 0.0.0.255 any eq 443\n  999 deny ip any any log\n```\n\nEvery ACL has an implicit deny at the end. Add an explicit logged deny when the\noperational goal includes observing misses, and confirm logging volume is safe.\n\n## ACL Placement Review\n\nBefore applying an ACL to an interface, answer these questions:\n\n- Which traffic direction is being filtered, `in` or `out`?\n- Is management traffic sourced from a known jump host or management subnet?\n- Is there an explicit permit for required routing, DNS, NTP, monitoring, or\n  application traffic?\n- Are hit counters available from a safe test source?\n- Is there a rollback command and an active console or out-of-band path?\n\nDo not test reachability by removing firewall or ACL protections. Read counters,\nlogs, and route state first.\n\n## Interface Hygiene\n\n```text\ninterface GigabitEthernet0\u002F1\n description UPLINK-TO-CORE\n switchport mode trunk\n switchport trunk allowed vlan 10,20,30\n switchport trunk native vlan 999\n no shutdown\n```\n\nUse clear descriptions, explicit switchport mode, and documented native VLANs.\nOn routed interfaces, confirm the mask, peer addressing, and routing process\nbefore assuming link state means forwarding is correct.\n\n## Change-Window Verification\n\nUse before\u002Fafter checks that match the actual change.\n\n```text\nshow running-config | section interface GigabitEthernet0\u002F1\nshow interfaces GigabitEthernet0\u002F1\nshow logging | include GigabitEthernet0\u002F1|changed state|line protocol\nshow ip route \u003Cprefix>\nshow ip access-lists \u003Cname>\n```\n\nFor routing changes, also capture neighbor state and route tables before and\nafter the change. For ACL changes, compare hit counters from a planned test\nsource rather than relying on a generic ping.\n\n## Anti-Patterns\n\n- Applying a generated config without a device-specific diff.\n- Saving configuration before post-change checks pass.\n- Using a subnet mask where IOS expects a wildcard mask.\n- Applying an ACL to the wrong interface direction.\n- Troubleshooting by disabling ACLs, route policies, or authentication.\n- Pasting full configs into public tools without sanitizing secrets and topology.\n\n## See Also\n\n- Agent: `network-config-reviewer`\n- Agent: `network-troubleshooter`\n- Skill: `network-config-validation`\n- Skill: `network-interface-health`\n","# Cisco IOS Patterns\n\nUse this skill when reviewing Cisco IOS or IOS-XE snippets, building a\nchange-window checklist, or explaining how to collect evidence from a router or\nswitch without making the incident worse.\n\n## When to Use\n\n- Reviewing IOS or IOS-XE configuration before a planned change.\n- Choosing read-only `show` commands for troubleshooting.\n- Checking ACL wildcard masks and interface direction.\n- Explaining global, interface, routing process, and line configuration modes.\n- Verifying that a change landed in running config and was saved intentionally.\n\n## Operating Rules\n\nTreat IOS examples as patterns, not paste-ready production changes. Confirm the\nplatform, interface names, current config, rollback path, and out-of-band access\nbefore making changes on a real device.\n\nPrefer this workflow:\n\n1. Capture current state with read-only commands.\n2. Review the exact candidate config.\n3. Confirm management access cannot be locked out.\n4. Apply the smallest change in a maintenance window.\n5. Re-read state, compare to the baseline, then save only after validation.\n\n## Mode Reference\n\n```text\nRouter> enable\nRouter# show running-config\nRouter# configure terminal\nRouter(config)# interface GigabitEthernet0\u002F1\nRouter(config-if)# description UPLINK-TO-CORE\nRouter(config-if)# no shutdown\nRouter(config-if)# exit\nRouter(config)# end\nRouter# show running-config interface GigabitEthernet0\u002F1\n```\n\n`running-config` is active memory. `startup-config` is what survives reload.\nDo not save a change just because a command was accepted; validate behavior\nfirst, then use `copy running-config startup-config` if the change is approved.\n\n## Read-Only Collection\n\n```text\nshow version\nshow inventory\nshow processes cpu sorted\nshow memory statistics\nshow logging\nshow running-config | section line vty\nshow running-config | section interface\nshow running-config | section router bgp\nshow ip interface brief\nshow interfaces\nshow interfaces status\nshow vlan brief\nshow mac address-table\nshow spanning-tree\nshow ip route\nshow ip protocols\nshow ip access-lists\nshow route-map\nshow ip prefix-list\n```\n\nCollect the specific section you need instead of dumping full config into a\nticket when the config may contain secrets, customer names, or private topology.\n\n## Wildcard Masks\n\nIOS ACL and many routing statements use wildcard masks, not subnet masks.\n\n```text\nSubnet mask       Wildcard mask\n255.255.255.255   0.0.0.0\n255.255.255.252   0.0.0.3\n255.255.255.0     0.0.0.255\n255.255.0.0       0.0.255.255\n```\n\nReview wildcard masks before deployment. A subnet mask accidentally used as a\nwildcard can match far more traffic than intended.\n\n```text\nip access-list extended WEB-IN\n  10 permit tcp 192.0.2.0 0.0.0.255 any eq 443\n  999 deny ip any any log\n```\n\nEvery ACL has an implicit deny at the end. Add an explicit logged deny when the\noperational goal includes observing misses, and confirm logging volume is safe.\n\n## ACL Placement Review\n\nBefore applying an ACL to an interface, answer these questions:\n\n- Which traffic direction is being filtered, `in` or `out`?\n- Is management traffic sourced from a known jump host or management subnet?\n- Is there an explicit permit for required routing, DNS, NTP, monitoring, or\n  application traffic?\n- Are hit counters available from a safe test source?\n- Is there a rollback command and an active console or out-of-band path?\n\nDo not test reachability by removing firewall or ACL protections. Read counters,\nlogs, and route state first.\n\n## Interface Hygiene\n\n```text\ninterface GigabitEthernet0\u002F1\n description UPLINK-TO-CORE\n switchport mode trunk\n switchport trunk allowed vlan 10,20,30\n switchport trunk native vlan 999\n no shutdown\n```\n\nUse clear descriptions, explicit switchport mode, and documented native VLANs.\nOn routed interfaces, confirm the mask, peer addressing, and routing process\nbefore assuming link state means forwarding is correct.\n\n## Change-Window Verification\n\nUse before\u002Fafter checks that match the actual change.\n\n```text\nshow running-config | section interface GigabitEthernet0\u002F1\nshow interfaces GigabitEthernet0\u002F1\nshow logging | include GigabitEthernet0\u002F1|changed state|line protocol\nshow ip route \u003Cprefix>\nshow ip access-lists \u003Cname>\n```\n\nFor routing changes, also capture neighbor state and route tables before and\nafter the change. For ACL changes, compare hit counters from a planned test\nsource rather than relying on a generic ping.\n\n## Anti-Patterns\n\n- Applying a generated config without a device-specific diff.\n- Saving configuration before post-change checks pass.\n- Using a subnet mask where IOS expects a wildcard mask.\n- Applying an ACL to the wrong interface direction.\n- Troubleshooting by disabling ACLs, route policies, or authentication.\n- Pasting full configs into public tools without sanitizing secrets and topology.\n\n## See Also\n\n- Agent: `network-config-reviewer`\n- Agent: `network-troubleshooter`\n- Skill: `network-config-validation`\n- Skill: `network-interface-health`\n",{"name":5,"metadata":24,"description":7},{"origin":25},"community","main","a73152352c0612252131e5cf84e91312a6cf17dc","devops-cloud\u002Fcisco-ios-patterns","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs","https:\u002F\u002Fgithub.com\u002FHenrique1601","https:\u002F\u002Fbezerraportifolio.netlify.app\u002F","Full Stack Developer | React, Next.js, TypeScript, Node.js & IA | Construindo produtos digitais e soluções SaaS","2026-11-15 02:56:04",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill cisco-ios-patterns",{"tool":40,"command":41},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill cisco-ios-patterns",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill cisco-ios-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fdevops-cloud\u002Fcisco-ios-patterns\u002FSKILL.md",true,[],[49,56,63,71,78,85],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7E2ANBW9V6AVX5JXNCEAWF8","rag-architect-agent","Agente Arquiteto de RAG, Embeddings & Busca Vetorial. Especialista em design e implementação de pipelines de Retrieval-Augmented Generation de alta fidelidade: chunking semântico, modelagem pgvector no PostgreSQL (Neon\u002FSupabase), busca híbrida (cosseno + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fcustom-agents\u002Frag-architect-agent\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7E29KKF8R02ZRGYE2MJM67G","rag-architecture-patterns","Padrões arquiteturais e implementação de pipelines RAG (Retrieval-Augmented Generation) de alta fidelidade para qualquer projeto ou sistema. Cobre chunking semântico, embeddings, busca híbrida (pgvector + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Frag-architecture-patterns\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7CWRA8E3BJ7CPY8N8EG28J1","skill-repair","Use this to fix and re-install agent skills that have failed installation.\nThis skill provides the necessary context and permissions to surgically update\nthe `manifest.json` after a fix has been applied.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fskill-repair\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7CWR66FZP8FA47WVZ4Z2EXC","security-scan","Scan your Claude Code configuration (.claude\u002F directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-scan\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7CWR0QPY58QPTR1P759TFNG","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CWQXCE40XWT4FZ3VWZFGDP","security-bounty-hunter","Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-bounty-hunter\u002FSKILL.md",[],[]]