[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FP4MR34BP1MCWB1ZRVFVQ":3,"skill-same:01M70FP4MR34BP1MCWB1ZRVFVQ":67},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M70FP4MR34BP1MCWB1ZRVFVQ","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.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fcisco-ios-patterns\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"cisco ios patterns","ios","patterns","cisco","when","writing","hierarchy","window","for","reading","interface","commands","show","community","verification","planning","config","change","safe","review","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. 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":44,"description":7},{"origin":32},"main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fcisco-ios-patterns",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill cisco-ios-patterns",{"tool":59,"command":60},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill cisco-ios-patterns",{"tool":62,"command":63},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill cisco-ios-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fcisco-ios-patterns\u002FSKILL.md",true,[],[68,76,84,91,98,105],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":75},"01M767791C1KRP2ZRW2Z73VZ5Q","system-lifecycle-designer","Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fsystem-lifecycle-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":83},"01M748ABPN5F1FANHH6HKZQMXT","style-sampling","Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for \"an episode of\", \"in the style of\", \"sample this style\", 「用这个风格做一集」. One video to copy is reverse-any-video.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Fstyle-sampling\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":83},"01M748A59V04PKW4HA0XQ81FGP","reverse-any-video","Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Freverse-any-video\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":83},"01M7487T50P55CSXMWXZ0G9KRG","typescript-patterns","TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftypescript-patterns\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":83},"01M7487ERZRGPC5NJ75077Y238","test-collaboration","Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit\u002Fintegration\u002Fcontract\u002FE2E\u002Fsmoke classification, bug-to-test regression protection, consumer\u002Fprovider contract testing, test-necessity review, and pre-delivery evidence review.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftest-collaboration\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":83},"01M748721J3GKR2WS6K0QWFC35","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fstory-lifecycle\u002FSKILL.md",[],[]]