skills/clementwalter/1password-credential-lookup/SKILL.md
This skill should be used when agents need to log into websites, retrieve passwords, or access credentials. CRITICAL - always use find_credential with the website URL, never guess item names.
npx skillsauth add aiskillstore/marketplace 1password-credential-lookupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
WRONG:
get_credential(item_name="github.com") ← NEVER DO THIS
get_credential(item_name="GitHub") ← NEVER DO THIS
RIGHT:
find_credential(url="github.com") ← CORRECT
find_credential(url="github.com", username="clementwalter") ← EVEN BETTER
When logging into a website, use find_credential with the domain.
1Password items have arbitrary names that don't match URLs. The find_credential tool searches by the URL field stored in 1Password, which matches the website you're visiting.
find_credential - PRIMARY TOOLUse this for ALL credential lookups:
find_credential(url="github.com")
find_credential(url="linkedin.com", username="[email protected]")
Parameters:
url (required): Domain of website (e.g., "github.com", "twitter.com")username (optional): Filter by username when multiple accounts existReturns:
{"username": "...", "password": "...", "item_name": "..."}list_items_for_url - When unsure which accountlist_items_for_url(url="github.com")
Shows all accounts for a domain with usernames. Use before find_credential if you don't know which account to use.
get_credential - RARELY NEEDEDOnly use if you have an exact item ID (like ct2jszznlzlp7r7jeb53rhy5li). Never pass URLs or guessed names.
When logging into github.com:
# Step 1: Get credentials for the domain
find_credential(url="github.com", username="clementwalter")
# If multiple accounts and no username filter:
# → Returns list: [{"username": "[email protected]"}, {"username": "[email protected]"}]
# → Pick one and retry with username filter
# Step 2: Use returned credentials to fill login form
These domains are treated as equivalent:
x.com ↔ twitter.com| Error | Solution |
| ---------------------- | ---------------------------------- |
| "No items found" | Check domain spelling |
| "Multiple items found" | Add username parameter to filter |
| "op CLI not installed" | User needs 1Password CLI |
| "Timed out" | User needs to run op signin |
NEVER do these:
get_credential(item_name="github.com") - URL is not an item nameget_credential(item_name="GitHub") - Guessed names don't workget_credential(item_name="my github") - Item names are arbitraryALWAYS do this:
find_credential(url="github.com") - Search by the website URLdevelopment
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.