Menú
Guide for optimizing LinkedIn profiles, creating professional content, and building strategic networking approaches for technology professionals.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Create, update, review, fix, or debug VS Code agent customization files (.instructions.md, .prompt.md, .agent.md, SKILL.md, copilot-instructions.md, AGENTS.md). Use for: saving coding preferences; troubleshooting why instructions/skills/agents are ignored or not invoked; configuring applyTo patterns; defining tool restrictions; creating custom agent modes or specialized workflows; packaging domain knowledge; fixing YAML frontmatter syntax.
Automated testing strategies for the Jump Start framework — secret scanning, type checking, smoke testing, and UAT coverage alignment. Use this skill when the Developer agent needs to validate code quality beyond unit tests, when security scanning is needed before commit, when type safety must be enforced, or when acceptance criteria coverage needs verification.
Structured techniques for eliciting, analyzing, and documenting software requirements from stakeholders, reducing ambiguity and missed scope.
AI-powered design intelligence for building professional UI/UX across multiple platforms and frameworks. Contains 67 styles, 96 colour palettes, 57 font pairings, 99 UX guidelines, and 25 chart types across 13 technology stacks with a searchable database and design system generator.
| name | |
| description | Guide for optimizing LinkedIn profiles, creating professional content, and building strategic networking approaches for technology professionals. |
This skill provides structured workflows for building and maintaining a strong LinkedIn presence, tailored for technology professionals.
Use the format: [Role] | [Specialty] | [Value Proposition]
Examples:
Avoid: Job title only, buzzword soup, or emoji-heavy headlines.
Keep under 2,000 characters. Write in first person. Avoid corporate jargon.
For each role, use the CAR format:
Limit to 3-4 bullet points per role. Lead with the most impactful result.
| Type | Purpose | Example |
|---|---|---|
| Insight | Share a lesson learned | "3 things I learned migrating to microservices" |
| Story | Humanize your experience | "My first production outage taught me..." |
| Resource | Help others | "Here's the checklist I use for code reviews" |
| Question | Start discussion | "How does your team handle on-call rotations?" |
Hi [Name], I came across your [post/talk/article] about [topic] and found [specific point] particularly insightful. I'm working on [related area] and would love to connect. — [Your name]