[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B7FXD7Q2NG4EP5X9EGGASH":3,"skill-same:01M7B7FXD7Q2NG4EP5X9EGGASH":99},{"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":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":63,"commitSha":64,"skillDirectory":65,"forksCount":13,"repositoryHtmlUrl":66,"repositoryHomepageUrl":6,"ownerHtmlUrl":67,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":68,"install":69,"resources":82},"01M7B7FXD7Q2NG4EP5X9EGGASH","implementing-llm-guardrails-for-security",null,"Implements input\u002Foutput validation guardrails for LLM applications using NVIDIA NeMo Guardrails (Colang), custom Python validators for PII detection, and the Guardrails AI framework, intercepting user inputs (prompt injection, PII, off-topic queries) and model outputs (hallucinations, toxic content, schema compliance). Use when adding safety controls to an LLM app\u002Fchatbot\u002FRAG pipeline or validating outputs conform to expected schemas.","vikasvardhanv\u002Fjerry_skills","vikasvardhanv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99010657?v=4","01M7B2B0VN78W7529RQX5BR6DZ","01M7B2B0WDNTXJHRK3QNPNWRP6",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-llm-guardrails-for-security\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-llm-guardrails-for-security\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-llm-guardrails-for-security\ndescription: 'Implements input\u002Foutput validation guardrails for LLM applications using\n  NVIDIA NeMo Guardrails (Colang), custom Python validators for PII detection, and\n  the Guardrails AI framework, intercepting user inputs (prompt injection, PII,\n  off-topic queries) and model outputs (hallucinations, toxic content, schema\n  compliance). Use when adding safety controls to an LLM app\u002Fchatbot\u002FRAG pipeline\n  or validating outputs conform to expected schemas.\n\n  '\ndomain: cybersecurity\nsubdomain: ai-security\ntags:\n- LLM-guardrails\n- NeMo-Guardrails\n- input-validation\n- output-filtering\n- AI-safety\nversion: 1.0.0\nauthor: mukul975\nlicense: Apache-2.0\natlas_techniques:\n- AML.T0051\n- AML.T0054\n- AML.T0056\n- AML.T0057\n- AML.T0062\nnist_ai_rmf:\n- GOVERN-1.1\n- GOVERN-6.1\n- MEASURE-2.7\n- MEASURE-2.5\n- MANAGE-2.4\nd3fend_techniques:\n- Content Validation\n- Content Filtering\n- Content Excision\n- Application Hardening\n- Execution Isolation\nnist_csf:\n- GV.OC-03\n- ID.RA-01\n- PR.PS-01\n- DE.AE-02\nmitre_attack:\n- T1078\n- T1190\n- T1059\n- T1055\n---\n# Implementing LLM Guardrails for Security\n\n## When to Use\n\n- Deploying a new LLM-powered application that processes user input and needs input\u002Foutput safety controls\n- Adding content policy enforcement to an existing chatbot or AI agent to comply with organizational policies\n- Implementing PII detection and redaction in LLM pipelines handling sensitive customer data\n- Building topic-restricted AI assistants that must refuse off-topic or disallowed queries\n- Validating that LLM responses conform to expected schemas before they reach downstream systems or users\n- Protecting RAG pipelines from indirect prompt injection in retrieved documents\n\n**Do not use** as a replacement for proper authentication, authorization, and network security controls. Guardrails are a defense-in-depth layer, not a perimeter defense. Not suitable for real-time content moderation of user-to-user communication without LLM involvement.\n\n## Prerequisites\n\n- Python 3.10+ with pip for installing guardrail dependencies\n- An OpenAI API key or local LLM endpoint for NeMo Guardrails self-check rails (set as `OPENAI_API_KEY` environment variable)\n- The `nemoguardrails` package for Colang-based guardrail definitions\n- The `guardrails-ai` package for structured output validation (optional, for JSON schema enforcement)\n- Familiarity with YAML configuration and basic Colang 2.0 syntax for defining rail flows\n\n## Workflow\n\n### Step 1: Install Guardrail Frameworks\n\nInstall the required Python packages:\n\n```bash\n# Core NeMo Guardrails library\npip install nemoguardrails\n\n# Guardrails AI for structured output validation (optional)\npip install guardrails-ai\n\n# Additional dependencies for PII detection and content analysis\npip install presidio-analyzer presidio-anonymizer spacy\npython -m spacy download en_core_web_lg\n```\n\n### Step 2: Run the Guardrails Security Agent\n\nThe agent implements a complete input\u002Foutput validation pipeline:\n\n```bash\n# Analyze a single input through all guardrail layers\npython agent.py --input \"Tell me how to hack into a system\"\n\n# Analyze input with a custom content policy file\npython agent.py --input \"Some text\" --policy policy.json\n\n# Scan a file of prompts through the guardrail pipeline\npython agent.py --file prompts.txt --mode full\n\n# Input-only validation (no LLM call, just check if input is safe)\npython agent.py --input \"Some text\" --mode input-only\n\n# Output validation mode (validate a pre-generated LLM response)\npython agent.py --input \"User question\" --response \"LLM response to validate\" --mode output-only\n\n# PII detection and redaction mode\npython agent.py --input \"My SSN is 123-45-6789 and email john@example.com\" --mode pii\n\n# JSON output for pipeline integration\npython agent.py --file prompts.txt --output json\n```\n\n### Step 3: Configure Content Policies\n\nCreate a JSON policy file defining allowed topics, blocked patterns, and PII categories:\n\n```json\n{\n  \"allowed_topics\": [\"customer_support\", \"product_info\", \"billing\"],\n  \"blocked_topics\": [\"politics\", \"violence\", \"illegal_activities\", \"competitor_products\"],\n  \"blocked_patterns\": [\"how to hack\", \"create malware\", \"bypass security\"],\n  \"pii_categories\": [\"PERSON\", \"EMAIL_ADDRESS\", \"PHONE_NUMBER\", \"US_SSN\", \"CREDIT_CARD\"],\n  \"max_output_length\": 2000,\n  \"require_grounded_response\": true\n}\n```\n\n### Step 4: Integrate NeMo Guardrails with Colang\n\nCreate a NeMo Guardrails configuration directory with `config.yml` and Colang flow files:\n\n```yaml\n# config.yml\nmodels:\n  - type: main\n    engine: openai\n    model: gpt-4o-mini\n\nrails:\n  input:\n    flows:\n      - self check input\n      - check jailbreak\n      - mask sensitive data on input\n  output:\n    flows:\n      - self check output\n      - check hallucination\n```\n\n```colang\n# rails.co - Colang 2.0 flow definitions\ndefine user ask about hacking\n  \"How do I hack into a system\"\n  \"Tell me how to break into a network\"\n  \"How to exploit vulnerabilities\"\n\ndefine bot refuse hacking request\n  \"I cannot provide instructions on unauthorized hacking or security exploitation.\n   If you are interested in cybersecurity, I can suggest legitimate learning resources\n   and ethical hacking certifications.\"\n\ndefine flow\n  user ask about hacking\n  bot refuse hacking request\n```\n\n### Step 5: Deploy as a Validation Middleware\n\nIntegrate the guardrails into your application as middleware:\n\n```python\nfrom agent import GuardrailsPipeline\n\npipeline = GuardrailsPipeline(policy_path=\"policy.json\")\n\n# Pre-LLM input validation\ninput_result = pipeline.validate_input(\"user message here\")\nif not input_result[\"safe\"]:\n    return input_result[\"blocked_reason\"]\n\n# Post-LLM output validation\nllm_response = your_llm.generate(input_result[\"sanitized_input\"])\noutput_result = pipeline.validate_output(llm_response, context=input_result)\nif not output_result[\"safe\"]:\n    return output_result[\"fallback_response\"]\n\nreturn output_result[\"validated_response\"]\n```\n\n### Step 6: Monitor Guardrail Effectiveness\n\nReview guardrail logs to track block rates, false positives, and bypass attempts:\n\n```bash\n# Generate a summary report from guardrail logs\npython agent.py --file interaction_logs.txt --mode full --output json > guardrail_audit.json\n```\n\n## Verification\n\n- [ ] Input guardrails correctly block known prompt injection patterns (system override, role-play escape, delimiter injection)\n- [ ] PII detection identifies and redacts email addresses, phone numbers, SSNs, and credit card numbers in user inputs\n- [ ] Topic restriction guardrails refuse off-policy queries and allow on-policy queries without false positives\n- [ ] Output guardrails detect and flag responses containing toxic content, PII leakage, or off-topic material\n- [ ] The guardrails pipeline adds less than 200ms of latency to the request\u002Fresponse cycle for input-only validation\n- [ ] JSON output mode produces valid, parseable JSON suitable for downstream monitoring dashboards\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **Input Rail** | A guardrail that intercepts and validates user input before it reaches the LLM, blocking injection attempts and redacting sensitive data |\n| **Output Rail** | A guardrail that validates LLM-generated output before it reaches the user, filtering toxic content and enforcing schema compliance |\n| **Colang** | NVIDIA's domain-specific language for defining conversational guardrail flows, with Python-like syntax for specifying user intent patterns and bot responses |\n| **PII Redaction** | The process of detecting and masking personally identifiable information (names, emails, SSNs) in text before processing |\n| **Content Policy** | A configuration file defining which topics, patterns, and content categories are allowed or blocked by the guardrail system |\n| **Self-Check Rail** | A NeMo Guardrails technique where the LLM itself evaluates whether its input or output violates defined policies |\n| **Hallucination Detection** | Output validation that checks whether the LLM response is grounded in the provided context, flagging fabricated claims |\n\n## Tools & Systems\n\n- **NVIDIA NeMo Guardrails**: Open-source toolkit for adding programmable input, dialog, and output rails to LLM applications using Colang flow definitions and YAML configuration\n- **Guardrails AI**: Python framework for structured output validation with a hub of pre-built validators for PII, toxicity, JSON schema compliance, and more\n- **Microsoft Presidio**: Open-source PII detection and anonymization engine supporting 30+ entity types with configurable NLP backends\n- **Colang 2.0**: Event-driven interaction modeling language for defining guardrail flows with Python-like syntax, supporting multi-turn dialog control\n- **OpenAI Guardrails Python**: OpenAI's client-side guardrails library for prompt injection detection and content policy enforcement\n","# Implementing LLM Guardrails for Security\n\n## When to Use\n\n- Deploying a new LLM-powered application that processes user input and needs input\u002Foutput safety controls\n- Adding content policy enforcement to an existing chatbot or AI agent to comply with organizational policies\n- Implementing PII detection and redaction in LLM pipelines handling sensitive customer data\n- Building topic-restricted AI assistants that must refuse off-topic or disallowed queries\n- Validating that LLM responses conform to expected schemas before they reach downstream systems or users\n- Protecting RAG pipelines from indirect prompt injection in retrieved documents\n\n**Do not use** as a replacement for proper authentication, authorization, and network security controls. Guardrails are a defense-in-depth layer, not a perimeter defense. Not suitable for real-time content moderation of user-to-user communication without LLM involvement.\n\n## Prerequisites\n\n- Python 3.10+ with pip for installing guardrail dependencies\n- An OpenAI API key or local LLM endpoint for NeMo Guardrails self-check rails (set as `OPENAI_API_KEY` environment variable)\n- The `nemoguardrails` package for Colang-based guardrail definitions\n- The `guardrails-ai` package for structured output validation (optional, for JSON schema enforcement)\n- Familiarity with YAML configuration and basic Colang 2.0 syntax for defining rail flows\n\n## Workflow\n\n### Step 1: Install Guardrail Frameworks\n\nInstall the required Python packages:\n\n```bash\n# Core NeMo Guardrails library\npip install nemoguardrails\n\n# Guardrails AI for structured output validation (optional)\npip install guardrails-ai\n\n# Additional dependencies for PII detection and content analysis\npip install presidio-analyzer presidio-anonymizer spacy\npython -m spacy download en_core_web_lg\n```\n\n### Step 2: Run the Guardrails Security Agent\n\nThe agent implements a complete input\u002Foutput validation pipeline:\n\n```bash\n# Analyze a single input through all guardrail layers\npython agent.py --input \"Tell me how to hack into a system\"\n\n# Analyze input with a custom content policy file\npython agent.py --input \"Some text\" --policy policy.json\n\n# Scan a file of prompts through the guardrail pipeline\npython agent.py --file prompts.txt --mode full\n\n# Input-only validation (no LLM call, just check if input is safe)\npython agent.py --input \"Some text\" --mode input-only\n\n# Output validation mode (validate a pre-generated LLM response)\npython agent.py --input \"User question\" --response \"LLM response to validate\" --mode output-only\n\n# PII detection and redaction mode\npython agent.py --input \"My SSN is 123-45-6789 and email john@example.com\" --mode pii\n\n# JSON output for pipeline integration\npython agent.py --file prompts.txt --output json\n```\n\n### Step 3: Configure Content Policies\n\nCreate a JSON policy file defining allowed topics, blocked patterns, and PII categories:\n\n```json\n{\n  \"allowed_topics\": [\"customer_support\", \"product_info\", \"billing\"],\n  \"blocked_topics\": [\"politics\", \"violence\", \"illegal_activities\", \"competitor_products\"],\n  \"blocked_patterns\": [\"how to hack\", \"create malware\", \"bypass security\"],\n  \"pii_categories\": [\"PERSON\", \"EMAIL_ADDRESS\", \"PHONE_NUMBER\", \"US_SSN\", \"CREDIT_CARD\"],\n  \"max_output_length\": 2000,\n  \"require_grounded_response\": true\n}\n```\n\n### Step 4: Integrate NeMo Guardrails with Colang\n\nCreate a NeMo Guardrails configuration directory with `config.yml` and Colang flow files:\n\n```yaml\n# config.yml\nmodels:\n  - type: main\n    engine: openai\n    model: gpt-4o-mini\n\nrails:\n  input:\n    flows:\n      - self check input\n      - check jailbreak\n      - mask sensitive data on input\n  output:\n    flows:\n      - self check output\n      - check hallucination\n```\n\n```colang\n# rails.co - Colang 2.0 flow definitions\ndefine user ask about hacking\n  \"How do I hack into a system\"\n  \"Tell me how to break into a network\"\n  \"How to exploit vulnerabilities\"\n\ndefine bot refuse hacking request\n  \"I cannot provide instructions on unauthorized hacking or security exploitation.\n   If you are interested in cybersecurity, I can suggest legitimate learning resources\n   and ethical hacking certifications.\"\n\ndefine flow\n  user ask about hacking\n  bot refuse hacking request\n```\n\n### Step 5: Deploy as a Validation Middleware\n\nIntegrate the guardrails into your application as middleware:\n\n```python\nfrom agent import GuardrailsPipeline\n\npipeline = GuardrailsPipeline(policy_path=\"policy.json\")\n\n# Pre-LLM input validation\ninput_result = pipeline.validate_input(\"user message here\")\nif not input_result[\"safe\"]:\n    return input_result[\"blocked_reason\"]\n\n# Post-LLM output validation\nllm_response = your_llm.generate(input_result[\"sanitized_input\"])\noutput_result = pipeline.validate_output(llm_response, context=input_result)\nif not output_result[\"safe\"]:\n    return output_result[\"fallback_response\"]\n\nreturn output_result[\"validated_response\"]\n```\n\n### Step 6: Monitor Guardrail Effectiveness\n\nReview guardrail logs to track block rates, false positives, and bypass attempts:\n\n```bash\n# Generate a summary report from guardrail logs\npython agent.py --file interaction_logs.txt --mode full --output json > guardrail_audit.json\n```\n\n## Verification\n\n- [ ] Input guardrails correctly block known prompt injection patterns (system override, role-play escape, delimiter injection)\n- [ ] PII detection identifies and redacts email addresses, phone numbers, SSNs, and credit card numbers in user inputs\n- [ ] Topic restriction guardrails refuse off-policy queries and allow on-policy queries without false positives\n- [ ] Output guardrails detect and flag responses containing toxic content, PII leakage, or off-topic material\n- [ ] The guardrails pipeline adds less than 200ms of latency to the request\u002Fresponse cycle for input-only validation\n- [ ] JSON output mode produces valid, parseable JSON suitable for downstream monitoring dashboards\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **Input Rail** | A guardrail that intercepts and validates user input before it reaches the LLM, blocking injection attempts and redacting sensitive data |\n| **Output Rail** | A guardrail that validates LLM-generated output before it reaches the user, filtering toxic content and enforcing schema compliance |\n| **Colang** | NVIDIA's domain-specific language for defining conversational guardrail flows, with Python-like syntax for specifying user intent patterns and bot responses |\n| **PII Redaction** | The process of detecting and masking personally identifiable information (names, emails, SSNs) in text before processing |\n| **Content Policy** | A configuration file defining which topics, patterns, and content categories are allowed or blocked by the guardrail system |\n| **Self-Check Rail** | A NeMo Guardrails technique where the LLM itself evaluates whether its input or output violates defined policies |\n| **Hallucination Detection** | Output validation that checks whether the LLM response is grounded in the provided context, flagging fabricated claims |\n\n## Tools & Systems\n\n- **NVIDIA NeMo Guardrails**: Open-source toolkit for adding programmable input, dialog, and output rails to LLM applications using Colang flow definitions and YAML configuration\n- **Guardrails AI**: Python framework for structured output validation with a hub of pre-built validators for PII, toxicity, JSON schema compliance, and more\n- **Microsoft Presidio**: Open-source PII detection and anonymization engine supporting 30+ entity types with configurable NLP backends\n- **Colang 2.0**: Event-driven interaction modeling language for defining guardrail flows with Python-like syntax, supporting multi-turn dialog control\n- **OpenAI Guardrails Python**: OpenAI's client-side guardrails library for prompt injection detection and content policy enforcement\n",{"name":5,"tags":24,"author":30,"domain":31,"license":14,"version":32,"nist_csf":33,"subdomain":38,"description":39,"nist_ai_rmf":40,"mitre_attack":46,"atlas_techniques":51,"d3fend_techniques":57},[25,26,27,28,29],"LLM-guardrails","NeMo-Guardrails","input-validation","output-filtering","AI-safety","mukul975","cybersecurity","1.0.0",[34,35,36,37],"GV.OC-03","ID.RA-01","PR.PS-01","DE.AE-02","ai-security","Implements input\u002Foutput validation guardrails for LLM applications using NVIDIA NeMo Guardrails (Colang), custom Python validators for PII detection, and the Guardrails AI framework, intercepting user inputs (prompt injection, PII, off-topic queries) and model outputs (hallucinations, toxic content, schema compliance). Use when adding safety controls to an LLM app\u002Fchatbot\u002FRAG pipeline or validating outputs conform to expected schemas.\n",[41,42,43,44,45],"GOVERN-1.1","GOVERN-6.1","MEASURE-2.7","MEASURE-2.5","MANAGE-2.4",[47,48,49,50],"T1078","T1190","T1059","T1055",[52,53,54,55,56],"AML.T0051","AML.T0054","AML.T0056","AML.T0057","AML.T0062",[58,59,60,61,62],"Content Validation","Content Filtering","Content Excision","Application Hardening","Execution Isolation","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-llm-guardrails-for-security","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill implementing-llm-guardrails-for-security",{"tool":75,"command":76},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill implementing-llm-guardrails-for-security",{"tool":78,"command":79},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill implementing-llm-guardrails-for-security","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-llm-guardrails-for-security\u002FSKILL.md",true,[83,87,93],{"path":84,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fapi-reference.md","REFERENCE","参考文档",7186,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-llm-guardrails-for-security\u002Freferences\u002Fapi-reference.md",{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Fagent.py","SCRIPT","脚本",22070,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fimplementing-llm-guardrails-for-security\u002Fscripts\u002Fagent.py",[100,108,115,122,129,136],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":104,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7BESR1CJ3H5SP9XM8KYJZ9W","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","MIT","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":104,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M7BES1YA6R97W7QPMFFM1PED","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":104,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M7BERNHYGY035AR00VRT03KE","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":104,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":19},"01M7BERCK1EAKTWW7R436WAR0J","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":104,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":19},"01M7BEQZAZAQRTXFJRY7RHV3TY","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":104,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":19},"01M7BEQKJ45K31QK5VRAQSVJCJ","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]