[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79FBMHX58R8EXWVF0TS3PBX":3,"skill-same:01M79FBMHX58R8EXWVF0TS3PBX":120},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M79FBMHX58R8EXWVF0TS3PBX","nature-paper2ppt",null,"Build a complete Nature-style Chinese PPTX presentation from a scientific paper, preprint, PDF, article text, figure legends, or reading notes. Use for journal club, group meeting, thesis seminar, paper sharing, conference or defense decks, and Chinese requests such as 论文做PPT、论文汇报、组会PPT、文献汇报、学术汇报、做幻灯片、读书报告PPT. It classifies paper type, builds an evidence-led story, selects key figures, writes Chinese slide content and speaker notes, creates the actual .pptx, and runs corrective QA for complete figure crops, stable alignment, text overflow, and de-templated Chinese academic expression. Also trigger when improving weak paper-to-PPT output with cropped figures, loose alignment, obvious AI-style wording, or heavy manual rework.","hamzabellouch\u002Fagent-skills","hamzabellouch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F237856042?v=4","01M79BRYW7XAMK3YDWQEMTWGWS","Hamza Bellouch","01M79BRYWXQV3JK2TGVTX8GN2A",8,"MIT","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FScience\u002FAcademic_Research_and_Methodology\u002Facademic-nature-nature-paper2ppt\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: nature-paper2ppt\ndescription: Build a complete Nature-style Chinese PPTX presentation from a scientific paper, preprint, PDF, article text, figure legends, or reading notes. Use for journal club, group meeting, thesis seminar, paper sharing, conference or defense decks, and Chinese requests such as 论文做PPT、论文汇报、组会PPT、文献汇报、学术汇报、做幻灯片、读书报告PPT. It classifies paper type, builds an evidence-led story, selects key figures, writes Chinese slide content and speaker notes, creates the actual .pptx, and runs corrective QA for complete figure crops, stable alignment, text overflow, and de-templated Chinese academic expression. Also trigger when improving weak paper-to-PPT output with cropped figures, loose alignment, obvious AI-style wording, or heavy manual rework.\n---\n\n# Paper-to-PPTX — Router\n\nThis skill is split into two layers:\n\n- A **static layer** under `static\u002F` that holds versioned, reusable content fragments (core principles, toolchain policy, the 9-step workflow, output\u002Fquality rules, and per-paper-type presentation arcs).\n- A **dynamic layer** (this file plus `manifest.yaml`) that detects the paper type and loads only the fragments needed for the current job. Deep design, figure, and self-review material lives in on-demand references.\n\nDo not try to apply the deck-building logic from memory or from this router. Always load fragments from disk as described below.\n\n## Routing protocol\n\nFollow these five steps every time the skill is invoked.\n\n### 1. Load the manifest and the core layer\n\nRead [manifest.yaml](manifest.yaml). It declares the `paper_type` axis, the allowed values, and the file paths each value maps to.\n\nAlso read every file listed under `always_load`. These hold the purpose and core principle, the lean operating mode and toolchain policy, the 9-step workflow spine, and the output\u002Fquality rules that apply to every deck, plus the shared Terminology Ledger used to keep technical terms consistent across slides.\n\n### 2. Classify the paper type\n\nDecide the `paper_type` value using the manifest's `detect:` hint and the source:\n\n- `discovery` — discovery \u002F mechanism papers (question-to-evidence arc). Default.\n- `methods` — methods \u002F AI \u002F tool \u002F algorithm papers (problem-to-solution arc).\n- `resource` — resource \u002F dataset \u002F atlas \u002F omics \u002F benchmark papers (workflow-to-validation arc).\n- `clinical` — clinical \u002F population \u002F intervention studies (design-to-inference arc).\n- `materials` — materials \u002F chemistry \u002F physics \u002F engineering papers (property-to-mechanism \u002F design-to-performance arc).\n- `review` — reviews \u002F perspectives \u002F commentaries \u002F meta-analyses (evidence-map arc).\n\nState the detected value in one short line to the user before designing slides, so they can correct you cheaply.\n\n### 3. Load the matching fragment\n\nRead the file mapped for the detected `paper_type`. It gives the presentation arc and how to adapt the default slide structure for this type. Do **not** read every fragment in `static\u002F`.\n\n### 4. Build the deck using the loaded material\n\nApply the loaded fragments in this priority order:\n\n1. Core principles (`core\u002Fprinciples.md`) — the argument is the spine; lean operating mode; accepted inputs; Chinese-by-default language rule.\n2. Toolchain policy and fast path (`core\u002Ftoolchain.md`) — cross-platform Python-first stack, default fast path.\n3. Paper-type arc (the loaded `paper_type` fragment) — narrative order and slide structure for this paper.\n4. Workflow (`core\u002Fworkflow.md`) — run the 9 steps end to end.\n5. Output and quality rules (`core\u002Foutput-and-quality.md`) — deliverables, quality gates, fallbacks.\n\nBuild the Terminology Ledger (`..\u002Fnature-shared\u002Fcore\u002Fterminology-ledger.md`) while reading the source, so model names, gene\u002Fprotein names, datasets, metrics, and abbreviations stay identical across every slide and speaker note.\n\nThe end product is a real `.pptx` deck, not an outline or script. Do not fabricate results, numbers, or figure details.\n\n### 5. Reach for references only when needed\n\nThe files under `references\u002F` are deep references, not defaults. Open them on demand per the `references.on_demand` table in the manifest:\n\n- composing\u002Fauditing slide layout, visual rhythm, typography, anti-template design, archetypes, on-slide text budget → `references\u002Fdesign-and-layout.md`.\n- selecting, extracting, cropping, and quality-checking figure\u002Ftable assets → `references\u002Ffigure-assets.md`.\n- running the self-review\u002Fcorrective revision loop, severity grading, programmatic PPTX checks, rendered-preview policy, and final verification → `references\u002Fself-review.md`.\n\nWhen a real PPTX has been generated, run `scripts\u002Faudit_pptx_quality.py` unless the file is unavailable. Treat high-severity findings as blockers, revise the deck, then re-run the audit and record the final result in `output\u002Fqa_report.md`.\n\n## Why this split\n\n- The static layer is versioned and reviewable. Adding a new paper-type arc is one new fragment plus one manifest line.\n- The dynamic layer keeps each invocation cheap: only the arc for this paper enters context up front; heavy design and QA material loads only when that step runs.\n- The router itself is short on purpose. Update fragments, not this file, when adding scope.\n- This structure mirrors `nature-writing`, `nature-polishing`, and `nature-reader` so shared content lives in `nature-shared\u002F`.\n","# Paper-to-PPTX — Router\n\nThis skill is split into two layers:\n\n- A **static layer** under `static\u002F` that holds versioned, reusable content fragments (core principles, toolchain policy, the 9-step workflow, output\u002Fquality rules, and per-paper-type presentation arcs).\n- A **dynamic layer** (this file plus `manifest.yaml`) that detects the paper type and loads only the fragments needed for the current job. Deep design, figure, and self-review material lives in on-demand references.\n\nDo not try to apply the deck-building logic from memory or from this router. Always load fragments from disk as described below.\n\n## Routing protocol\n\nFollow these five steps every time the skill is invoked.\n\n### 1. Load the manifest and the core layer\n\nRead [manifest.yaml](manifest.yaml). It declares the `paper_type` axis, the allowed values, and the file paths each value maps to.\n\nAlso read every file listed under `always_load`. These hold the purpose and core principle, the lean operating mode and toolchain policy, the 9-step workflow spine, and the output\u002Fquality rules that apply to every deck, plus the shared Terminology Ledger used to keep technical terms consistent across slides.\n\n### 2. Classify the paper type\n\nDecide the `paper_type` value using the manifest's `detect:` hint and the source:\n\n- `discovery` — discovery \u002F mechanism papers (question-to-evidence arc). Default.\n- `methods` — methods \u002F AI \u002F tool \u002F algorithm papers (problem-to-solution arc).\n- `resource` — resource \u002F dataset \u002F atlas \u002F omics \u002F benchmark papers (workflow-to-validation arc).\n- `clinical` — clinical \u002F population \u002F intervention studies (design-to-inference arc).\n- `materials` — materials \u002F chemistry \u002F physics \u002F engineering papers (property-to-mechanism \u002F design-to-performance arc).\n- `review` — reviews \u002F perspectives \u002F commentaries \u002F meta-analyses (evidence-map arc).\n\nState the detected value in one short line to the user before designing slides, so they can correct you cheaply.\n\n### 3. Load the matching fragment\n\nRead the file mapped for the detected `paper_type`. It gives the presentation arc and how to adapt the default slide structure for this type. Do **not** read every fragment in `static\u002F`.\n\n### 4. Build the deck using the loaded material\n\nApply the loaded fragments in this priority order:\n\n1. Core principles (`core\u002Fprinciples.md`) — the argument is the spine; lean operating mode; accepted inputs; Chinese-by-default language rule.\n2. Toolchain policy and fast path (`core\u002Ftoolchain.md`) — cross-platform Python-first stack, default fast path.\n3. Paper-type arc (the loaded `paper_type` fragment) — narrative order and slide structure for this paper.\n4. Workflow (`core\u002Fworkflow.md`) — run the 9 steps end to end.\n5. Output and quality rules (`core\u002Foutput-and-quality.md`) — deliverables, quality gates, fallbacks.\n\nBuild the Terminology Ledger (`..\u002Fnature-shared\u002Fcore\u002Fterminology-ledger.md`) while reading the source, so model names, gene\u002Fprotein names, datasets, metrics, and abbreviations stay identical across every slide and speaker note.\n\nThe end product is a real `.pptx` deck, not an outline or script. Do not fabricate results, numbers, or figure details.\n\n### 5. Reach for references only when needed\n\nThe files under `references\u002F` are deep references, not defaults. Open them on demand per the `references.on_demand` table in the manifest:\n\n- composing\u002Fauditing slide layout, visual rhythm, typography, anti-template design, archetypes, on-slide text budget → `references\u002Fdesign-and-layout.md`.\n- selecting, extracting, cropping, and quality-checking figure\u002Ftable assets → `references\u002Ffigure-assets.md`.\n- running the self-review\u002Fcorrective revision loop, severity grading, programmatic PPTX checks, rendered-preview policy, and final verification → `references\u002Fself-review.md`.\n\nWhen a real PPTX has been generated, run `scripts\u002Faudit_pptx_quality.py` unless the file is unavailable. Treat high-severity findings as blockers, revise the deck, then re-run the audit and record the final result in `output\u002Fqa_report.md`.\n\n## Why this split\n\n- The static layer is versioned and reviewable. Adding a new paper-type arc is one new fragment plus one manifest line.\n- The dynamic layer keeps each invocation cheap: only the arc for this paper enters context up front; heavy design and QA material loads only when that step runs.\n- The router itself is short on purpose. Update fragments, not this file, when adding scope.\n- This structure mirrors `nature-writing`, `nature-polishing`, and `nature-reader` so shared content lives in `nature-shared\u002F`.\n",{"name":5,"description":7},"main","e905af21e5f1e1c3ca605e9656c3a7930360a84e","Science\u002FAcademic_Research_and_Methodology\u002Facademic-nature-nature-paper2ppt",1,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills","https:\u002F\u002Fhamzabellouch.github.io\u002F","https:\u002F\u002Fgithub.com\u002Fhamzabellouch","hamzabellouch.github.io","CEO & Founder of @tknoglobal | Researcher in Technology & Applied Sciences.","2026-10-17 03:20:19",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add hamzabellouch\u002Fagent-skills --skill nature-paper2ppt",{"tool":40,"command":41},"bunx","bunx skills add hamzabellouch\u002Fagent-skills --skill nature-paper2ppt",{"tool":43,"command":44},"pnpm","pnpm dlx skills add hamzabellouch\u002Fagent-skills --skill nature-paper2ppt","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FScience\u002FAcademic_Research_and_Methodology\u002Facademic-nature-nature-paper2ppt\u002FSKILL.md",true,[48,54,58,62,66,70,74,80,84,88,92,96,100,104,108,112,116],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"manifest.yaml","REFERENCE","参考文档",2860,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FScience\u002FAcademic_Research_and_Methodology\u002Facademic-nature-nature-paper2ppt\u002Fmanifest.yaml",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"README_EN.md",2139,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FScience\u002FAcademic_Research_and_Methodology\u002Facademic-nature-nature-paper2ppt\u002FREADME_EN.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"README.md",1851,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FScience\u002FAcademic_Research_and_Methodology\u002Facademic-nature-nature-paper2ppt\u002FREADME.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fdesign-and-layout.md",14025,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FScience\u002FAcademic_Research_and_Methodology\u002Facademic-nature-nature-paper2ppt\u002Freferences\u002Fdesign-and-layout.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Ffigure-assets.md",4693,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FScience\u002FAcademic_Research_and_Methodology\u002Facademic-nature-nature-paper2ppt\u002Freferences\u002Ffigure-assets.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fself-review.md",6586,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FScience\u002FAcademic_Research_and_Methodology\u002Facademic-nature-nature-paper2ppt\u002Freferences\u002Fself-review.md",{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"scripts\u002Faudit_pptx_quality.py","SCRIPT","脚本",13114,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FScience\u002FAcademic_Research_and_Methodology\u002Facademic-nature-nature-paper2ppt\u002Fscripts\u002Faudit_pptx_quality.py",{"path":81,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":82,"sourceHtmlUrl":83},"static\u002Fcore\u002Foutput-and-quality.md",5020,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FScience\u002FAcademic_Research_and_Methodology\u002Facademic-nature-nature-paper2ppt\u002Fstatic\u002Fcore\u002Foutput-and-quality.md",{"path":85,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":86,"sourceHtmlUrl":87},"static\u002Fcore\u002Fprinciples.md",3005,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FScience\u002FAcademic_Research_and_Methodology\u002Facademic-nature-nature-paper2ppt\u002Fstatic\u002Fcore\u002Fprinciples.md",{"path":89,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":90,"sourceHtmlUrl":91},"static\u002Fcore\u002Ftoolchain.md",2601,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FScience\u002FAcademic_Research_and_Methodology\u002Facademic-nature-nature-paper2ppt\u002Fstatic\u002Fcore\u002Ftoolchain.md",{"path":93,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":94,"sourceHtmlUrl":95},"static\u002Fcore\u002Fworkflow.md",6350,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FScience\u002FAcademic_Research_and_Methodology\u002Facademic-nature-nature-paper2ppt\u002Fstatic\u002Fcore\u002Fworkflow.md",{"path":97,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":98,"sourceHtmlUrl":99},"static\u002Ffragments\u002Fpaper_type\u002Fclinical.md",1210,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FScience\u002FAcademic_Research_and_Methodology\u002Facademic-nature-nature-paper2ppt\u002Fstatic\u002Ffragments\u002Fpaper_type\u002Fclinical.md",{"path":101,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":102,"sourceHtmlUrl":103},"static\u002Ffragments\u002Fpaper_type\u002Fdiscovery.md",1300,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FScience\u002FAcademic_Research_and_Methodology\u002Facademic-nature-nature-paper2ppt\u002Fstatic\u002Ffragments\u002Fpaper_type\u002Fdiscovery.md",{"path":105,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":106,"sourceHtmlUrl":107},"static\u002Ffragments\u002Fpaper_type\u002Fmaterials.md",1221,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FScience\u002FAcademic_Research_and_Methodology\u002Facademic-nature-nature-paper2ppt\u002Fstatic\u002Ffragments\u002Fpaper_type\u002Fmaterials.md",{"path":109,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":110,"sourceHtmlUrl":111},"static\u002Ffragments\u002Fpaper_type\u002Fmethods.md",1275,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FScience\u002FAcademic_Research_and_Methodology\u002Facademic-nature-nature-paper2ppt\u002Fstatic\u002Ffragments\u002Fpaper_type\u002Fmethods.md",{"path":113,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":114,"sourceHtmlUrl":115},"static\u002Ffragments\u002Fpaper_type\u002Fresource.md",1162,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FScience\u002FAcademic_Research_and_Methodology\u002Facademic-nature-nature-paper2ppt\u002Fstatic\u002Ffragments\u002Fpaper_type\u002Fresource.md",{"path":117,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":118,"sourceHtmlUrl":119},"static\u002Ffragments\u002Fpaper_type\u002Freview.md",1035,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FScience\u002FAcademic_Research_and_Methodology\u002Facademic-nature-nature-paper2ppt\u002Fstatic\u002Ffragments\u002Fpaper_type\u002Freview.md",[121,128,135,142,149,156],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":19},"01M79FHH2H815A9TAP6WNKH4Q8","security-audit","Comprehensive security guidance, source code audit, vulnerability assessment, and penetration test review for codebases, APIs, microservices, CLI tools, libraries, and LLM-backed applications. Triggers on requests to audit a codebase, conduct security reviews, find vulnerabilities or flaws, pen-test source code, or when the user asks in Arabic (فحص أمني، تدقيق الكود أمنياً، مراجعة الثغرات، فحص أمان المشروع). Supports Guidance mode (focused review) and Full Audit mode (deterministic 6-phase harness).","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FSecurity_Audit_and_Code_Review\u002Fsecurity-audit\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":19},"01M79FHBGXVBY6VQ1X7ETAZMF1","malware-analysis-reversing","Production malware analysis workflows, reverse engineering methodologies, isolated sandbox triage, static\u002Fdynamic binary analysis, memory forensics, and YARA detection rule authoring.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FOffensive_Security_and_Pentesting\u002Fmalware-analysis-reversing\u002FSKILL.md",[],[],{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":19},"01M79FH6EACDR801TZCE4R8SAC","application-security-pentesting","Production Application Security (AppSec) standards, OWASP Top 10 vulnerability remediation, SAST\u002FDAST pipeline integration, secure code review, threat modeling, and defensive security posture.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FOffensive_Security_and_Pentesting\u002Fapplication-security-pentesting\u002FSKILL.md",[],[],{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":19},"01M79FH0VKVT44FK923K520ZQA","oauth2-oidc-security-flows","Implement enterprise OAuth 2.1 and OpenID Connect (OIDC) authorization code flow with Proof Key for Code Exchange (PKCE), state and nonce verification, refresh token rotation, token revocation, and centralized IdP federation (Keycloak, Auth0, Okta). Trigger when building secure authentication, single sign-on (SSO), or third-party delegated authorization.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FIdentity_and_Access_Management_IAM\u002Foauth2-oidc-security-flows\u002FSKILL.md",[],[],{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":19},"01M79FGVVB3R4T88XXD8FRSV5B","jwt-session-management-hardening","Harden JWT-based authentication and session lifecycles using asymmetric signing (RS256\u002FEdDSA), JWKS rotation, strict claims validation, Redis-backed sliding window sessions, revocation lists, and secure HttpOnly cookie storage. Trigger when implementing token validation, session revocation, or hardening API authentication.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FIdentity_and_Access_Management_IAM\u002Fjwt-session-management-hardening\u002FSKILL.md",[],[],{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":19},"01M79FGNCPZ85CVEY0B3NE4H3B","soc2-compliance-automation","Best practices for implementing SOC 2 Type II compliance controls, continuous evidence collection, infrastructure policy-as-code, and automated security monitoring. Use when automating Trust Services Criteria (Security, Availability, Confidentiality, Processing Integrity, Privacy), audit logging, IAM least privilege, or CI\u002FCD security gates.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FGovernance_Compliance_and_Legal_Tech\u002Fsoc2-compliance-automation\u002FSKILL.md",[],[]]