Menu

Individual skill

fewshot_attempt_03

0upvotes

Not available

experiments/claude_code_kimi2_6_enabled/reports/skills/task_group_001/fewshot/fewshot_attempt_03/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
Yes
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
# HarborCRM Task Solving Skill

## Environment & API Basics

- **Base URL**: `http://34.46.77.124:8001` (from `environment_access.md`; do not use localhost).
- Only query endpoint paths and entity IDs **explicitly named in the task prompt**. Do not call global list/index endpoints to discover IDs.
- Read the task prompt carefully to identify which endpoints to call and which entity IDs are relevant.

## Core Workflow

1. Read the task `prompt.txt` to understand the business objective, relevant API endpoints, and required output schema.
2. Read `input/payloads/answer_template.json` to understand the exact required JSON structure, field types, enums, and ordering rules.
3. Query only the explicitly named API endpoints to gather data.
4. Apply business rules from the prompt (qualification criteria, exclusion reasons, ranking logic, CRM actions, opportunity sizing, deduplication rules, etc.).
5. Produce a single JSON object conforming exactly to the answer template. No prose outside the JSON.
Back to top