agentsclimarketplace
Sign in

Signal intake

Skill brian8a1/senso-agent-skills/skills/signal-intake

Bring a source that is currently outside Senso into Signals with the correct provenance and routing. Use when the user has customer feedback, interview or usability notes, a support conversation, incident, bug report, metric, document, or external finding that should become Senso evidence or reusable Knowledge.From its SKILL.md

Install
npx -y skills add brian8a1/senso-agent-skills --skill signal-intake

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, 408 tokens by cl100k_base, as published. Nobody here has run it

Add a source to Signals

Turn source material already in front of the user into traceable Senso evidence. Preserve the source; let Senso classify and cluster it.

Procedure

  1. Identify the source type and its provenance: who or what produced it, when, and where the original can be opened.
  2. Choose one capture path:
    • Customer statement, bug, observation, or metric anomaly: call senso_capture with mode: signal.
    • Interview transcript, research notes, product documentation, or reusable context: call senso_capture with mode: knowledge and the appropriate capture_mode.
    • External query or metric that supports a Living Document: resolve the document with senso_lookup, then call senso_capture with mode: add_artefact_evidence.
    • A human-approved replacement for a Living Document: use mode: update_artefact; never overwrite one merely to append a finding.
  3. Preserve exact quotes only when supplied. Summarize observations in your own words and distinguish them from metrics.
  4. Include source URLs, filenames, account/customer context, date, and analysis warnings when available.
  5. Report what entered Signals or Knowledge, its Senso reference, and any processing still running.

Routing rules

  • Use modality Q for a supplied quote, O for an observation or incident, and M for a measured value. Omit modality when uncertain so Senso can infer it.
  • Use signals_only for source evidence, context_only for reusable background, and context_and_signals for research material that should do both.
  • Do not manually create an Opportunity, Solution, priority, or outcome. Those are later human/product interactions.
  • Do not convert an agent opinion into customer evidence.

Result

Leave the user with a concise receipt: source captured, destination in Senso, created reference, and anything that still needs Signal Review.

What ships with it: 1 file

478 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 326,764. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.