agentsclimarketplace

And intake

Skill Andiedie/skills/skills/ai-native-development/and-intake

Personal agent skills for coding agents, installable with npx skills.

Install
npx -y skills add Andiedie/skills --skill and-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.

What its author says it does

Copied from the file, not written here

Record raw requests as clear workflow work records.

SKILL.md

3.0 KB, 610 tokens by cl100k_base, as published. Nobody here has run it

AND Intake

Capture one raw request, bug report, feedback item, or explicitly presented external PR as durable workflow state. Preserve the signal and its uncertainty; and-triage decides what should happen next.

Workflow Contract

Use and-workflow-contract with work-records.md for Locate Work and Write Work Record before writing durable state.

If repository setup or the contract is unavailable, route to setup-and or report the missing skill. If GitHub is temporarily unwritable, return a ready-to-file draft and the exact access problem.

Process

  1. Resolve one work record.

    • Resolve one GitHub repository from the explicit target, current repository, remotes, or repository instructions.
    • Update the record the user identifies by issue number, URL, work ID, or path.
    • Update an obvious exact duplicate. Create a new record for distinct work, linking related work when useful.
    • Ask only when choosing the wrong create or update target would create durable workflow-state noise.
    • When the user explicitly presents a PR, read external-pr-signals.md before resolving its work record.
    • Completion criterion: one repository and exactly one create or update target are known.

  2. Publish the raw signal.

    • Inspect only the evidence needed to record the signal accurately: a fitting repository template, named files or commands, errors, URLs, and obvious exact duplicates.
    • Use a fitting repository template, or a concise shape that preserves the source signal, evidence, and open questions.
    • Write a concise title that names the requested change or observed problem, and preserve material source wording, observed behavior, errors, logs, screenshots, environment details, links, and commands.
    • Keep user or author claims, Agent-confirmed facts, inferences, and unknowns distinguishable where they differ. Leave unknowns unresolved.
    • Use the user's language and repository conventions, while keeping literal identifiers verbatim.
    • Create or update the GitHub work record. New work receives only needs-triage; updates merge new durable information without changing existing workflow decisions.
    • Leave routing and scope questions in the record for and-triage rather than settling them during intake.
    • Completion criterion: GitHub contains one evidence-faithful record of the raw signal, or the user has a complete ready-to-file draft and a concrete write blocker.

  3. Report the result.

    • Return a short receipt with created, updated, or draft; the work link or ID when available; the final title; and and-triage as the next skill.
    • When no write occurred, include the access or target problem that prevented it. Keep the full record, evidence, and open questions in GitHub or the draft.
    • Completion criterion: the receipt truthfully distinguishes a durable create or update from an unwritten draft.

Keep looking

Skills are one crate of 328,083. 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.