Add app agents list and prompt, and document prompts for the seed agents
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
4e3c3f130e
commit
2534803df3
3 files changed
+106
-6
No files matched your search
+18
-6
@@ -69,7 +69,7 @@ summarise:
|
||||
enabled: false
|
||||
model: claude-haiku-4-5-20251001
|
||||
|
||||
# A role and each agent's intent as vectors, for the fit term of a score
|
||||
# A role and each agent's prompts as vectors, for the fit term of a score
|
||||
# (app/jobs/embed.py). Needs the `embeddings` extra; without it `embed` posts
|
||||
# a notice and scores leave fit out. Changing the model re-embeds.
|
||||
# multilingual-e5-small, not English-only MiniLM, because the corpus is now
|
||||
@@ -117,15 +117,27 @@ sources: {}
|
||||
# 0.65}; measured for "Copenhagen engineering" on 16,841 open roles, 0.55
|
||||
# admits about 300 roles to extract and 0.65 about 35 to summarise. A wide
|
||||
# monitoring search lowers the bars and raises the counts, a narrow hunt the
|
||||
# reverse. An agent without an intent has no fit and feeds neither stage.
|
||||
# reverse. An agent without a prompt that has text has no fit and feeds
|
||||
# neither stage.
|
||||
# prompts is a list of {name, text}, each what the agent looks for; a role's
|
||||
# fit is its best prompt's, so one agent can hunt several kinds of role
|
||||
# without blending them into one paragraph. Votes, gates and limits stay the
|
||||
# agent's, shared by its prompts. intent, as in config.yaml, is one prompt
|
||||
# named after the agent.
|
||||
# The Search agents sub-tab lists and edits them; the order menu on Roles
|
||||
# picks one by name. Two more, beside the starter in config.yaml:
|
||||
agents: []
|
||||
# - name: Remote from Europe
|
||||
# intent: >-
|
||||
# Staff or lead engineer role, fully remote from Europe. Platform and
|
||||
# infrastructure work, distributed systems, developer tooling, technical
|
||||
# leadership across teams.
|
||||
# prompts:
|
||||
# - name: Platform lead
|
||||
# text: >-
|
||||
# Staff or lead engineer role, fully remote from Europe. Platform and
|
||||
# infrastructure work, distributed systems, developer tooling,
|
||||
# technical leadership across teams.
|
||||
# - name: Forward deployed
|
||||
# text: >-
|
||||
# Forward deployed or solutions engineering lead, fully remote from
|
||||
# Europe. Hands-on with customers' systems, owns technical delivery.
|
||||
# gates:
|
||||
# - {field: remote, values: [remote], mode: require}
|
||||
# - {field: country, values: [AT, BE, BG, HR, CY, CZ, DK, EE, FI, FR, DE, GR, HU, IE, IT,
|
||||
|
||||
Reference in new issue
Block a user