fredrikaverpil/aip
stow/shared/.claude/skills/aip/SKILL.md
Google API Improvement Proposals (AIP) reference. Use BEFORE designing or reviewing APIs, protobuf definitions, or any work involving Google API design standards. Fetches relevant AIP rules from https://google.aip.dev for the task at hand.
$ install --global
skillsauthnpx skillsauth add fredrikaverpil/dotfiles aipInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 4, 2026, 11:47 PM9.5s1 file scanned
SKILL.md
- name:
- aip
- description:
- Google API Improvement Proposals (AIP) reference. Use BEFORE designing or reviewing APIs, protobuf definitions, or any work involving Google API design standards. Fetches relevant AIP rules from https://google.aip.dev for the task at hand.
Google API Improvement Proposals (AIP)
When working on API design, protobuf definitions, or any task involving Google API standards, refresh your understanding of the relevant AIP rules.
Critical Rule
NEVER assume you know what an AIP rule says from memory. Always fetch and read the actual AIP documentation before applying or referencing any rule. Your memory of AIP rules may be inaccurate or outdated.
Process
- Browse the AIP index - Go to https://google.aip.dev/general to see all available AIP guidelines
- Identify relevant AIPs - Based on the task at hand, determine which AIP rules may apply
- Fetch and read the relevant AIPs - Use WebFetch to retrieve the specific AIP pages. Do NOT skip this step, even if you think you know what the rule says
- Apply the standards - Ensure your work follows the AIP guidelines as documented
When to Invoke This Skill
- Designing new API endpoints or protobuf messages
- Reviewing API changes in PRs
- Implementing resource-oriented services
- Naming fields, methods, or resources
- Working with
google.apiannotations
Related Skills
fredrikaverpil/aip
development
VerifiedTrustedCommunity
Google API Improvement Proposals (AIP) reference. Use BEFORE designing or reviewing APIs, protobuf definitions, or any work involving Google API design standards. Fetches relevant AIP rules from https://google.aip.dev for the task at hand.
222SKILL.mdUpdated Apr 16, 2026
fredrikaverpil/nvim-plugin
tools
VerifiedTrustedCommunity
Guide for writing Neovim plugins in Lua following official Neovim conventions (https://neovim.io/doc/user/lua-plugin/). Use this skill whenever the user is creating, modifying, or reviewing a Neovim plugin — including when they mention plugin structure, ftplugin, health checks, keymaps, setup() functions, vimdoc, LuaCATS annotations, or lazy loading in the context of Neovim plugin development. Also trigger when the user is working in a directory that looks like a Neovim plugin (contains plugin/, lua/, ftplugin/ subdirectories).
217SKILL.mdUpdated Apr 14, 2026
fredrikaverpil/nvim-config
tools
VerifiedTrustedCommunity
Native Neovim config idioms and conventions — use whenever writing, reviewing, or modifying any Neovim configuration that uses Neovim's built-in conventions WITHOUT a plugin manager framework (no lazy.nvim, packer, etc.). Covers directory structure, vim.pack plugin management, lsp/ auto-discovery, plugin/ loading order, keymaps, and standard paths. Trigger on any task involving init.lua, plugin/*.lua, lsp/*.lua, vim.pack.add(), vim.lsp.enable(), or "native neovim config" — even if the user just says "add a plugin" or "configure LSP" in a native-style config.
217SKILL.mdUpdated Apr 14, 2026
fredrikaverpil/codebase-audit
development
VerifiedTrustedCommunity
Analyze a git repo's history to surface high-churn files, ownership risks, bug hotspots, momentum trends, and firefighting patterns. Use this skill whenever the user wants to understand a codebase, assess repo health, or orient themselves before reading code — even if they don't explicitly say "audit".
217SKILL.mdUpdated Apr 14, 2026