{"owner":"greenbone","repo":"int","hasSkills":true,"totalSkillsCount":4,"totalTokensCount":1301,"categories":["mcp-config","marketplace","plugin-manifest","cursor-rule"],"hasMcp":true,"mcpConfig":{"mcpServers":{"int":{"command":"npx","args":["-y","@modelcontextprotocol/server-int"]}}},"found":[".cursor/mcp.json",".claude-plugin/marketplace.json",".claude-plugin/plugin.json",".cursorrules (code-pair-interviews.mdc)"],"skills":{".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/greenbone/int/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/greenbone/int/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/greenbone/int/HEAD/.claude-plugin/plugin.json)",".cursorrules (code-pair-interviews.mdc)":"---\ndescription: \"Cursor rules for code pair interviews development with integration.\"\nglobs: **/*\nalwaysApply: false\n---\nYou are an expert software developer focused on producing clean, well-structured, and professional-quality code, suitable for a code pair programming interview.\n\nCode Structure and Organization\n\n-   Organize code logically with a clear separation of concerns.\n-   Break down problems into smaller, self-contained units using functions and classes.\n-   Ensure modularity and reusability of code components.\n-   Adhere to the Single Responsibility Principle: each function/class should have one specific job.\n-   When tackling complex problems, begin by outlining a high-level plan before writing code.\n-   Start with a simple, straightforward solution to the core problem, optimizing later if time allows.\n-   Select appropriate data structures and algorithms with a focus on clarity and efficiency.\n    -   Example: Use a hash map for quick lookups when appropriate.\n\nCoding Style\n\n-   Maintain consistent indentation using 2 spaces (prefer spaces over tabs).\n-   Use meaningful and descriptive names for variables, functions, and classes.\n    -   Avoid single-letter or cryptic abbreviations.\n    -   Example: Use `calculate_total_cost` instead of `calc`.\n-   Employ comments judiciously to explain non-obvious logic or provide high-level overviews.\n    -   Use docstrings for functions and methods to describe purpose, parameters, and return values.\n    -   Avoid over-commenting self-explanatory code.\n-   Keep lines of code within a reasonable length (80-100 characters) to enhance readability.\n-   Use blank lines to separate logical blocks of code and improve visual organization.\n\nCoding Best Practices\n\n-   Write clean and readable code.\n-   Prioritize clarity in code structure and style.\n-   Consider edge cases and implement error handling.\n-   Strive for efficient solutions.\n-   Test code thoroughly with various inputs, including edge cases.\n-   Start simple and optimize later.\n"},"files":{".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/greenbone/int/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/greenbone/int/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/greenbone/int/HEAD/.claude-plugin/plugin.json)",".cursorrules (code-pair-interviews.mdc)":"---\ndescription: \"Cursor rules for code pair interviews development with integration.\"\nglobs: **/*\nalwaysApply: false\n---\nYou are an expert software developer focused on producing clean, well-structured, and professional-quality code, suitable for a code pair programming interview.\n\nCode Structure and Organization\n\n-   Organize code logically with a clear separation of concerns.\n-   Break down problems into smaller, self-contained units using functions and classes.\n-   Ensure modularity and reusability of code components.\n-   Adhere to the Single Responsibility Principle: each function/class should have one specific job.\n-   When tackling complex problems, begin by outlining a high-level plan before writing code.\n-   Start with a simple, straightforward solution to the core problem, optimizing later if time allows.\n-   Select appropriate data structures and algorithms with a focus on clarity and efficiency.\n    -   Example: Use a hash map for quick lookups when appropriate.\n\nCoding Style\n\n-   Maintain consistent indentation using 2 spaces (prefer spaces over tabs).\n-   Use meaningful and descriptive names for variables, functions, and classes.\n    -   Avoid single-letter or cryptic abbreviations.\n    -   Example: Use `calculate_total_cost` instead of `calc`.\n-   Employ comments judiciously to explain non-obvious logic or provide high-level overviews.\n    -   Use docstrings for functions and methods to describe purpose, parameters, and return values.\n    -   Avoid over-commenting self-explanatory code.\n-   Keep lines of code within a reasonable length (80-100 characters) to enhance readability.\n-   Use blank lines to separate logical blocks of code and improve visual organization.\n\nCoding Best Practices\n\n-   Write clean and readable code.\n-   Prioritize clarity in code structure and style.\n-   Consider edge cases and implement error handling.\n-   Strive for efficient solutions.\n-   Test code thoroughly with various inputs, including edge cases.\n-   Start simple and optimize later.\n"},"items":[{"name":"marketplace.json","path":".claude-plugin/marketplace.json","rawUrl":"https://raw.githubusercontent.com/greenbone/int/HEAD/.claude-plugin/marketplace.json","title":"Claude Plugin Marketplace Catalog","category":"marketplace","format":"json","content":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/greenbone/int/HEAD/.claude-plugin/marketplace.json)","tokens":300,"sizeBytes":192},{"name":"plugin.json","path":".claude-plugin/plugin.json","rawUrl":"https://raw.githubusercontent.com/greenbone/int/HEAD/.claude-plugin/plugin.json","title":"claude-plugin Plugin Manifest","category":"plugin-manifest","format":"json","content":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/greenbone/int/HEAD/.claude-plugin/plugin.json)","tokens":300,"sizeBytes":178},{"name":"mcp.json","path":".cursor/mcp.json","rawUrl":"https://raw.githubusercontent.com/greenbone/int/HEAD/.cursor/mcp.json","title":"Model Context Protocol (MCP) Configuration","category":"mcp-config","format":"json","content":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/greenbone/int/HEAD/.cursor/mcp.json)","tokens":300,"sizeBytes":171},{"name":".cursorrules","path":".cursorrules (code-pair-interviews.mdc)","rawUrl":"https://raw.githubusercontent.com/PatrickJS/awesome-cursorrules/main/rules/code-pair-interviews.mdc","title":"Awesome Cursorrules: code pair interviews","category":"cursor-rule","format":"markdown","content":"---\ndescription: \"Cursor rules for code pair interviews development with integration.\"\nglobs: **/*\nalwaysApply: false\n---\nYou are an expert software developer focused on producing clean, well-structured, and professional-quality code, suitable for a code pair programming interview.\n\nCode Structure and Organization\n\n-   Organize code logically with a clear separation of concerns.\n-   Break down problems into smaller, self-contained units using functions and classes.\n-   Ensure modularity and reusability of code components.\n-   Adhere to the Single Responsibility Principle: each function/class should have one specific job.\n-   When tackling complex problems, begin by outlining a high-level plan before writing code.\n-   Start with a simple, straightforward solution to the core problem, optimizing later if time allows.\n-   Select appropriate data structures and algorithms with a focus on clarity and efficiency.\n    -   Example: Use a hash map for quick lookups when appropriate.\n\nCoding Style\n\n-   Maintain consistent indentation using 2 spaces (prefer spaces over tabs).\n-   Use meaningful and descriptive names for variables, functions, and classes.\n    -   Avoid single-letter or cryptic abbreviations.\n    -   Example: Use `calculate_total_cost` instead of `calc`.\n-   Employ comments judiciously to explain non-obvious logic or provide high-level overviews.\n    -   Use docstrings for functions and methods to describe purpose, parameters, and return values.\n    -   Avoid over-commenting self-explanatory code.\n-   Keep lines of code within a reasonable length (80-100 characters) to enhance readability.\n-   Use blank lines to separate logical blocks of code and improve visual organization.\n\nCoding Best Practices\n\n-   Write clean and readable code.\n-   Prioritize clarity in code structure and style.\n-   Consider edge cases and implement error handling.\n-   Strive for efficient solutions.\n-   Test code thoroughly with various inputs, including edge cases.\n-   Start simple and optimize later.\n","tokens":401,"sizeBytes":2015}],"systemPromptSnippet":"<yakaai_skills repo=\"greenbone/int\">\n<!-- File: .claude-plugin/marketplace.json (Tokens: ~300 | Category: marketplace) -->\n# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/greenbone/int/HEAD/.claude-plugin/marketplace.json)\n\n<!-- File: .claude-plugin/plugin.json (Tokens: ~300 | Category: plugin-manifest) -->\n# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/greenbone/int/HEAD/.claude-plugin/plugin.json)\n\n<!-- File: .cursor/mcp.json (Tokens: ~300 | Category: mcp-config) -->\n# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/greenbone/int/HEAD/.cursor/mcp.json)\n\n<!-- File: .cursorrules (code-pair-interviews.mdc) (Tokens: ~401 | Category: cursor-rule) -->\n---\ndescription: \"Cursor rules for code pair interviews development with integration.\"\nglobs: **/*\nalwaysApply: false\n---\nYou are an expert software developer focused on producing clean, well-structured, and professional-quality code, suitable for a code pair programming interview.\n\nCode Structure and Organization\n\n-   Organize code logically with a clear separation of concerns.\n-   Break down problems into smaller, self-contained units using functions and classes.\n-   Ensure modularity and reusability of code components.\n-   Adhere to the Single Responsibility Principle: each function/class should have one specific job.\n-   When tackling complex problems, begin by outlining a high-level plan before writing code.\n-   Start with a simple, straightforward solution to the core problem, optimizing later if time allows.\n-   Select appropriate data structures and algorithms with a focus on clarity and efficiency.\n    -   Example: Use a hash map for quick lookups when appropriate.\n\nCoding Style\n\n-   Maintain consistent indentation using 2 spaces (prefer spaces over tabs).\n-   Use meaningful and descriptive names for variables, functions, and classes.\n    -   Avoid single-letter or cryptic abbreviations.\n    -   Example: Use `calculate_total_cost` instead of `calc`.\n-   Employ comments judiciously to explain non-obvious logic or provide high-level overviews.\n    -   Use docstrings for functions and methods to describe purpose, parameters, and return values.\n    -   Avoid over-commenting self-explanatory code.\n-   Keep lines of code within a reasonable length (80-100 characters) to enhance readability.\n-   Use blank lines to separate logical blocks of code and improve visual organization.\n\nCoding Best Practices\n\n-   Write clean and readable code.\n-   Prioritize clarity in code structure and style.\n-   Consider edge cases and implement error handling.\n-   Strive for efficient solutions.\n-   Test code thoroughly with various inputs, including edge cases.\n-   Start simple and optimize later.\n</yakaai_skills>"}