generate-candidate-fields
Skill2 starsChanged 6 months agoApache-2.0View on GitHub
Propose 3-8 candidate research fields based on the full ActorProfile. When user wants to explore beyond their current stack, use other ActorProfile signals (intentionality, boundary) to determine exploration space. Free exploration within the boundary.
In this repository32 other files it gives its agents.
- actor-profilingSkill
- and-or-decomposeSkill
- ask-constraintsSkill
- ask-decomposition-validationSkill
- ask-intentionalitySkill
- ask-obstacle-acceptanceSkill
- assess-obstacle-severitySkill
- broad-paper-searchSkill
- broad-web-searchSkill
- clarify-resourcesSkill
- cold-startSkill
- crystallize-north-starSkill
- deep-web-searchSkill
- direction-narrowingSkill
- explore-resumeSkill
- feasibility-checkSkill
- final-validationSkill
- formulate-top-goalSkill
- generate-research-briefSkill
- goal-decompositionSkill
- hot-startSkill
- identify-obstaclesSkill
- landscape-reconnaissanceSkill
- landscape-synthesisSkill
- north-star-crystallizationSkill
- north-star-synthesisSkill
- obstacle-analysisSkill
- present-and-askSkill
- present-candidatesSkill
- propose-mitigationsSkill
- validate-leavesSkill
- warm-startSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
When user wants to explore beyond their current stack, use boundary + intentionality to determine the exploration space.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Generate Candidate Fields
Generate candidate research fields for the user to explore.
Execution
Subagent — spawned via subagent-spawning/spawn-agent skill.
Input
ActorProfile (full, as formatted text).
Output
3-8 candidate fields, each with a one-line rationale for why this user could enter it.
Key Behavior
When user wants to explore beyond their current stack, use boundary + intentionality to determine the exploration space. Don't limit to skills-only matching.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.