DavidROliverBA/ArchitectKB / .claude/skills/weblink
weblink
Verified/weblink
Save a URL as a weblink note with analysis and summary.
Usage
/weblink <url>
/weblink <url> <optional title>
Examples
/weblink https://github.com/anthropics/claude-code
/weblink https://aws.amazon.com/bedrock/ AWS Bedrock Service
Instructions
-
Fetch and analyse the URL:
- Use WebFetch to retrieve the page content
- Extract: title, author, source/domain, main content
- ALWAYS provide analysis - this is mandatory, not optional
-
Generate analysis (REQUIRED):
- Write a 2-3 sentence summary of what the resource is
- Extract 4-8 key points as bullet points
- Identify relevance to your organization/Solutions Architecture work where applicable
- Note any technical details (technologies, integrations, versions)
-
Generate filename:
Weblink - {{title}}.md -
Create weblink in vault root:
---
type: Weblink
title: {{title}}
created: {{DATE}}
modified: {{DATE}}
tags: [{{relevant tags}}]
url: {{url}}
domain: {{domain}}
author: {{author or null}}
source: {{source name}}
---
# {{title}}
## Source
- **URL:** {{url}}
- **Author:** {{author}}
- **Source:** {{source}}
## Summary
{{2-3 sentence summary of the resource}}
## Key Points
- {{key point 1}}
- {{key point 2}}
- {{key point 3}}
- {{...more as relevant}}
## Relevance to your organization
{{How this relates to YourOrg work, if applicable. Remove section if not relevant.}}
## Related
- {{wiki-links to related notes in vault}}
-
Tag extraction:
- Identify 2-5 relevant tags from content
- Use existing vault tags where possible (check other notes)
- Common tags: AWS, SAP, MCP, AI, architecture, integration, security
-
Find related notes:
- Search vault for related topics
- Add wiki-links to relevant existing notes
- Consider: projects, technologies, people, other weblinks
-
After creating:
- Confirm creation with file path
- Show brief summary of what was saved
- Mention key relevance if applicable
Quality Standards
- Never create a weblink without fetching and analysing the content first
- Always include a meaningful summary (not just the page title)
- Always extract key points - minimum 3, maximum 8
- Check for existing related notes to link to
- Use UK English throughout
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |