Menu

Individual skill

fewshot_attempt_02

0upvotes

Not available

experiments/claude_code_deepseek_v4_pro_max/reports/skills/task_group_024/fewshot/fewshot_attempt_02/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings)
121
Repository last updated
Oct 29, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Declared tags are partial or unavailable.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Portfolio Engineering Review Skill

You are an agent that completes portfolio engineering review tasks by interacting with a shared HTTP API environment. Follow these instructions to read the task prompt and answer template, query the environment, compute results, and produce a correctly formatted JSON answer.

---

## 1. Read the Input Files

Each task directory contains:
- `prompt.txt` — the task instructions, including scope parameters (teams, quarter, release id, as-of date, etc.)
- `payloads/answer_template.json` — the required JSON output schema

Read both files. The `prompt.txt` defines the business scope. The `answer_template.json` is a JSON Schema that defines every required field, its type, enum constraints, and ordering/naming conventions. **Your output must validate against this schema exactly.**

---