[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FD4V02S10RGWDVQKSQ18SF":3,"skill-same:01M7FD4V02S10RGWDVQKSQ18SF":49},{"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":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7FD4V02S10RGWDVQKSQ18SF","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. Use when reading, writing, or reviewing Cisco IOS \u002F IOS-XE configuration or planning a change window.","siddu1004\u002FSFP","siddu1004","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260113491?v=4","01M7F8W1SAJAR49097VRTE1TW5","Siddhardh Vanguri","01M7F8W1SYGY7JE15AHAECCT9R",5,"MIT","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fnetworking\u002Fskills\u002Fcisco-ios-patterns\u002FSKILL.md",[],[],"2026-11-16 10:05:34",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. Use when reading, writing, or reviewing Cisco IOS \u002F IOS-XE configuration or planning a change window.\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","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fnetworking\u002Fskills\u002Fcisco-ios-patterns",0,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fsfp-hive","https:\u002F\u002Fgithub.com\u002Fsiddu1004","I am a student at Amrita Vishwa Vidyapeetham pursuing my BTECH degree in Electronics and Electrical Engineering (2024-2028).","2026-11-09 16:04:40",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add siddu1004\u002FSFP --skill cisco-ios-patterns",{"tool":41,"command":42},"bunx","bunx skills add siddu1004\u002FSFP --skill cisco-ios-patterns",{"tool":44,"command":45},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill cisco-ios-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fnetworking\u002Fskills\u002Fcisco-ios-patterns\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7FEEDADZBNBVY19H3XZKCBQ","scientific-schematics","Generates scientific diagram drafts using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.7 Flash for quality review. Refines when the review requests improvement, with at most two generations. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways, and complex scientific visualizations.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fscientific-schematics\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7FEE0JS04FE58MST48D0MMC","polyhaven-texture-apply","Apply realistic PBR textures from PolyHaven to any Blender object. Supports metals, wood, concrete, fabric, and more. Trigger when asked to texture an object, apply a material from PolyHaven, make something look like metal\u002Fwood\u002Fmarble, or change object surface.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-texture-apply\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7FEDJRWV194TY411WVRS84W","polyhaven-studio-setup","Set up a professional product photography studio in Blender using PolyHaven HDRIs and PBR ground materials. Trigger when asked to create a studio setup, add HDRI lighting, set up product photography, or create a showroom scene.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-studio-setup\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},"01M7FED5H2FGS50XGETMGSM0RV","polyhaven-scene-builder","Build complete product scenes using PolyHaven assets — HDRI environment, textured ground\u002Fpedestal, and optional props from the 3D model library. Trigger when asked to build a product scene, create a showcase setup, add a pedestal, or compose a product shot.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-scene-builder\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},"01M7FECSNZ2CJA7Z8TPE5R844R","polyhaven-material-swap","Cycle through multiple PolyHaven materials on a product and render each variant. Great for showing color\u002Ffinish options. Trigger when asked to show material variants, swap textures, create color options, show finish comparisons, or render product in different materials.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-material-swap\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},"01M7FECBPQ6YWH48PYAMS0C5CE","polyhaven-hdri-showcase","Render the same product across multiple HDRI environments and output a comparison grid. Trigger when asked to compare lighting setups, test different environments, show product in multiple settings, or create an HDRI comparison.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-hdri-showcase\u002FSKILL.md",[],[]]