outbound-ip
Get the current public/outbound IP address of this machine using a reliable shell workflow with multiple fallback endpoints. Use when users ask for outbound IP, public IP, WAN IP, egress IP, or need IP checks before firewall/network allowlisting.
90
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels at trigger term coverage and completeness with an explicit 'Use when' clause. The description clearly defines its niche and provides multiple natural language variations users might employ. Minor improvement could be made by listing more specific actions or fallback methods used.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (public IP retrieval) and mentions 'multiple fallback endpoints' and 'shell workflow', but doesn't list specific concrete actions beyond 'get the current public/outbound IP address'. Could be more specific about what fallback methods are used. | 2 / 3 |
Completeness | Clearly answers both what ('Get the current public/outbound IP address using a reliable shell workflow with multiple fallback endpoints') and when ('Use when users ask for outbound IP, public IP, WAN IP, egress IP, or need IP checks before firewall/network allowlisting'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'outbound IP', 'public IP', 'WAN IP', 'egress IP', 'IP checks', 'firewall/network allowlisting'. These are all realistic variations a user might use when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on public/outbound IP retrieval. The specific trigger terms (WAN IP, egress IP, allowlisting) make it unlikely to conflict with general networking or system information skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, concise skill that efficiently delegates to a helper script and provides clear usage instructions. The content respects token budget and provides actionable guidance. Minor improvement could be made by integrating error handling into the workflow steps rather than as a separate note.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean content that assumes Claude's competence. No unnecessary explanations of what public IPs are or how shell scripts work. Every line serves a purpose. | 3 / 3 |
Actionability | Provides the exact command to run with clear flag options (--family 4/6, --json). The instruction to return the IP 'exactly as printed' is specific and unambiguous. | 3 / 3 |
Workflow Clarity | Simple two-step workflow is clear, but lacks explicit validation or error handling steps. The 'if all providers fail' note is mentioned but not integrated into a proper error recovery workflow. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the structure is appropriate. Quick workflow section followed by notes for edge cases. No need for external references given the scope. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- gitstua/stu-skills
- Commit
8dd0dc8
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.