[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JCQC5ZDM9G5YM2R85C8M1F":3,"skill-same:01M6JCQC5ZDM9G5YM2R85C8M1F":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M6JCQC5ZDM9G5YM2R85C8M1F","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.","S3YED\u002Fappie-kit","S3YED","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62743867?v=4","01M6JBKBRRVP6KMS0VWZ27T3R6","01M6JBKBX0KG30284PW1DBYJT1",14,"MIT","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fecc\u002Fcisco-ios-patterns\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"cisco ios patterns","ios","cisco","patterns","show","window","for","interface","hygiene","commands","review","community","ACL","verification","config","change","safe","2026-11-10 10:12:30",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.\norigin: 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,"origin":29,"description":7},"master","8ec37df6d71fb664ea19d32c079e7d3ff931a8e0","skills\u002Fecc\u002Fcisco-ios-patterns",3,"https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit","https:\u002F\u002Fweblyfe.ai","https:\u002F\u002Fgithub.com\u002FS3YED","2026-08-27 01:54:02",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add S3YED\u002Fappie-kit --skill cisco-ios-patterns",{"tool":54,"command":55},"bunx","bunx skills add S3YED\u002Fappie-kit --skill cisco-ios-patterns",{"tool":57,"command":58},"pnpm","pnpm dlx skills add S3YED\u002Fappie-kit --skill cisco-ios-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fecc\u002Fcisco-ios-patterns\u002FSKILL.md",true,[],[63,99,134,160,191,214],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":80,"publishedAt":35},"01M6JFD4M6N4DSGC7TXEJ5R3J2","ai-music","AI music generation and audio tools: HeartMuLa lyrics-to-music generation, songwriting craft (+ Suno prompts), and audio spectrogram\u002Ffeature visualization.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fwethlete\u002Fai-music\u002FSKILL.md",[69,74,77],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":75,"categoryName":76,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":78,"categoryName":79,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000023","Skill与智能体开发",[81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98],"music","ai music","humanizer","visualization","Tools","Audio","hermes","hermes agent","songwriting","suno","lyrics","prompts","heartmula","craft","generation","feature","ai music generation","music generation",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":113,"publishedAt":35},"01M6JFCZE4XNFQFMNZDHKHT5V5","agentic-webdesign-design-system-ingestion","Use v0 Design Systems 2.0, Bolt Design System Agents, or Lovable to generate production UI from a client's real design system components — not generic Tailwind. Use when building a client website where brand consistency matters.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-design-system-ingestion\u002FSKILL.md",[105,108],{"categoryNo":106,"categoryName":107,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133],"design","agentic","design system","system","ingestion","webdesign","agentic webdesign design system ingestion","components","generate","design systems","website","ui","Tailwind","bolt","lovable","v0","design-system","wed","design system components","appie",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":142,"publishedAt":35},"01M6JFCVPX3913CFAS6QQJ33ZB","agentic-webdesign-agent-elements","Use 21st.dev Agent Elements — 25 shadcn\u002Fui components purpose-built for AI agent UIs. Tool cards (Bash, Edit, Search, Plan, Subagent, MCP), chat, input, streaming. Open source, shadcn-registry install, no runtime lock-in.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fweb-design\u002Fagentic-webdesign-agent-elements\u002FSKILL.md",[140,141],{"categoryNo":78,"categoryName":79,"taxonomyType":72,"taxonomyTypeDesc":73},{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},[115,143,119,144,145,146,121,147,148,149,150,151,152,153,154,155,156,157,158,159],"elements","agentic webdesign agent elements","MCP","ai agent","registry","search","streaming","open source","open","Bash","plan","subagent","edit","install","input","lock","source",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":170,"publishedAt":35},"01M6JFCQC7H65M9QJ6TRE71BS1","vercel-deployment","Deploy static sites and frontends to Vercel — handles both CLI and REST API paths, including the CLI token sanitization workaround.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fvercel-deployment\u002FSKILL.md",[166,169],{"categoryNo":167,"categoryName":168,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":78,"categoryName":79,"taxonomyType":72,"taxonomyTypeDesc":73},[171,172,173,174,175,176,177,178,179,180,181,182,183,184,185,186,187,188,189,190],"deployment","vercel deployment","vercel","macos","cli","linux","windows","deploy","vercel deploy","REST","api","site","deploy to vercel","token","rest api","host","sites","paths","sanitization","static site",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":198,"publishedAt":35},"01M6JFCM4SMTXBM5A01BK2YQG1","software-quality-workflows","Umbrella workflow for TDD, debugging, code simplification, spikes, pre-commit review, and debugger-assisted investigation.","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Fsoftware-quality-workflows\u002FSKILL.md",[197],{"categoryNo":78,"categoryName":79,"taxonomyType":72,"taxonomyTypeDesc":73},[199,200,201,202,28,203,204,205,206,207,208,209,210,211,212,213,24],"workflows","quality","software","software quality workflows","tdd","workflow","commit","debugging","code","debugger","pre-commit","investigation","code simplification","user","simplification",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":227,"publishedAt":35},"01M6JFCGD0M6CEATY01W7YN6DB","react-component-refactoring","Safely refactor large React components into smaller, maintainable pieces using proven patterns","https:\u002F\u002Fgithub.com\u002FS3YED\u002Fappie-kit\u002Fblob\u002Fmaster\u002Fskills\u002Fsoftware-development\u002Freact-component-refactoring\u002FSKILL.md",[220,223,226],{"categoryNo":221,"categoryName":222,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":224,"categoryName":225,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":78,"categoryName":79,"taxonomyType":72,"taxonomyTypeDesc":73},[228,229,230,231,232,233,234,235,174,34,236,121,237,177,238,207,239,240,21,241],"react","component","refactoring","component refactoring","react component","react component refactoring","frontend","writing","typescript","react components","modular","refactor","simplify","test-driven-development"]