opportunity-report-next-steps-one — for Claude Code opportunity-report-next-steps-one, career-path-2026, community, for Claude Code, ide skills, career-planning, job-search, next_action, next_action_date, contacts[]

v1.0.0
GitHub

About this Skill

Ideal for AI agents that need report — next steps for one opportunity. opportunity-report-next-steps-one is an AI agent skill for report — next steps for one opportunity.

Features

Report — next steps for one opportunity
Role: Assistant — career / opportunity tracking (see docs/AGENT ROLES.md).
data/private/opportunities.yaml (private)
Output skeleton: templates/opportunity report next steps one.md
Select the record by id : <OPPORTUNITY ID (or company + role if user specifies — resolve ambiguity).

# Core Topics

for Claude Code career-planning job-search next_action next_action_date contacts[]
ferez96 ferez96
[4]
[0]
Updated: 4/29/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 8/11

This page remains useful for teams, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
8/11
Quality Score
39
Canonical Locale
en
Detected Body Locale
en

Ideal for AI agents that need report — next steps for one opportunity. opportunity-report-next-steps-one is an AI agent skill for report — next steps for one opportunity.

Core Value

opportunity-report-next-steps-one helps agents report — next steps for one opportunity. Design your career path: benchmark roles, track progress, execute weekly with data-driven insights. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Ideal Agent Persona

Ideal for AI agents that need report — next steps for one opportunity.

↓ Capabilities Granted for opportunity-report-next-steps-one

Applying Report — next steps for one opportunity
Applying Role: Assistant — career / opportunity tracking (see docs/AGENT ROLES.md)
Applying data/private/opportunities.yaml (private)

! Prerequisites & Limits

  • Output: Markdown for reports/private/opportunity-next-steps-<id -<YYYY-MM-DD .md or paste-only.
  • Output: Markdown for reports/private/opportunity-next-steps-<id -<YYYY-MM-DD .md or paste-only
  • Do not add general career advice, invented timelines, or assumed details not present in the data

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team workflows, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is opportunity-report-next-steps-one?

Ideal for AI agents that need report — next steps for one opportunity. opportunity-report-next-steps-one is an AI agent skill for report — next steps for one opportunity.

How do I install opportunity-report-next-steps-one?

Run the command: npx killer-skills add ferez96/career-path-2026. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for opportunity-report-next-steps-one?

Key use cases include: Applying Report — next steps for one opportunity, Applying Role: Assistant — career / opportunity tracking (see docs/AGENT ROLES.md), Applying data/private/opportunities.yaml (private).

Which IDEs are compatible with opportunity-report-next-steps-one?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for opportunity-report-next-steps-one?

Output: Markdown for reports/private/opportunity-next-steps-<id -<YYYY-MM-DD .md or paste-only.. Output: Markdown for reports/private/opportunity-next-steps-<id -<YYYY-MM-DD .md or paste-only. Do not add general career advice, invented timelines, or assumed details not present in the data.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add ferez96/career-path-2026. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use opportunity-report-next-steps-one immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

opportunity-report-next-steps-one

Install opportunity-report-next-steps-one, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before...

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Report — next steps for one opportunity

Role: Assistant — career / opportunity tracking (see docs/AGENT_ROLES.md).

Context to load:

  • data/private/opportunities.yaml (private)
  • Output skeleton: templates/opportunity_report_next_steps_one.md

Task:

  1. Select the record by id: <OPPORTUNITY_ID> (or company + role if user specifies — resolve ambiguity).
  2. Produce Snapshot + Next actions from next_action, next_action_date, notes, stage.
  3. Populate Contacts table from contacts[]; if empty, write "None recorded."
  4. Populate Check here (manual) table from links; if empty, write "None recorded."
  5. Add Blockers / risks from notes and stage.
  6. Add Suggested 24–72h moves aligned with the workflow style in docs/cursor/workflows.md (Workflow 2).
  7. Assumptions / Risk.

Output: Markdown for reports/private/opportunity-next-steps-<id>-<YYYY-MM-DD>.md or paste-only.

Constraints:

  • Full detail stays private; sanitize before any public reports/briefs/ excerpt.
  • Do not fabricate. Every sentence in the report must be traceable to a field in the YAML record (stage, next_action, notes, history, contacts, links). Do not add general career advice, invented timelines, or assumed details not present in the data.
  • Missing data → state it explicitly. If a section has no supporting data, write "No data recorded." Do not fill the gap with plausible-sounding content.
  • Assumptions section is mandatory. Any interpretation beyond a direct field read (e.g. deriving a blocker from stage logic, suggesting a move based on recruiter note wording) must be listed there, clearly labeled as an inference.

My inputs (collect, confirm, or ask):

  • If opportunity id (or company + role) is not in memory, chat, or unambiguous from opportunities.yaml: ask before generating the report.
  • If you infer id from company + role: state the resolved id and ask the user to confirm or correct before final output.
  • Opportunity id (or company + role): <...>

Related Skills

Looking for an alternative to opportunity-report-next-steps-one or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

openclaw-release-maintainer is an AI agent skill for openclaw release maintainer.

★ 333.8k
⑂ 0
AI

nextjs-turbopack

[ Featured ]
Logo of affaan-m
affaan-m

nextjs-turbopack is an AI agent skill for next.js and turbopack.

★ 169.5k
⑂ 0
Productivity

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

flags is an AI agent skill for use this skill when adding or changing framework feature flags in next.js internals.

★ 138.4k
⑂ 0
Browser