本文へ移動
cccskills
無料GitHub で公開

rseng-discovery

Covers discovering the research landscape around a topic or project: finding relevant publications (OpenAlex, arXiv, Zenodo, JOSS, Semantic Scholar, Google Scholar) and finding related software - libraries, packages, tools, platforms and competitor or alternative projects - across software registries, archives, package indexes, public forges and curated awesome lists. Use when the user asks what exists on a topic, wants related work, prior art, alternatives or competitors surveyed, needs a state-of-the-field picture for a paper or proposal, or is about to build something whose neighbors are unknown. (RSD-based reuse suggestions with bundled snapshots are rseng-software-reuse; adoption vetting is rseng-dependency-management; verifying found references is rseng-citation-hygiene.)

日本語の概要は準備中です。原文の説明を表示しています。

fdiblen/rseng-agent-skillsスター 24(GitHub 24 + cccskills 0)
連携ツールHugging Face

実行スコア 未検証

インストール方法を見る

含まれるファイル(2)

  • SKILL.md6.1 KB
  • references.md628 B

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Discovery: publications and software around a topic

Most research work begins in a landscape someone else has already mapped in part. Discovery is the deliberate survey of that landscape before building, writing or claiming novelty: the publications that define the state of the field, and the software that already solves pieces of the problem. Doing it early is cheaper than discovering a competitor in review, and the survey itself becomes reusable material for the paper's related-work section and the proposal's state of the art.

Finding publications

Work from open, keyless APIs first; they make searches reproducible and scriptable:

  • OpenAlex covers most of the scholarly record with abstracts, citation links and topic filters; Crossref serves DOI metadata; Semantic Scholar adds influence signals and TLDRs; arXiv covers preprints in its fields. Zenodo and JOSS matter specifically for research software: JOSS papers ARE software descriptions, and Zenodo records often carry the software itself.
  • Google Scholar casts the widest net (theses, reports, gray literature) but has no API and rate-limits scraping; use it interactively for coverage checks, not in pipelines.
  • Snowball in both directions from the two or three most relevant hits: who do they cite (backward), who cites them (forward - OpenAlex and Semantic Scholar both serve citing works). One good seed paper beats twenty keyword guesses.
  • Search by concept variants, not one phrasing: field synonyms, British/American spellings, method names old and new - and record the queries used, so the search is repeatable and its gaps are visible (rseng-reproducibility's spirit applied to searching).

Finding software

Cast several nets; each finds things the others miss:

  • Research software registries: Research Software Directory instances (rseng-software-reuse ships offline snapshots and the search discipline), domain registries (bio.tools for life sciences, ASCL for astronomy, and their field equivalents).
  • Package indexes for the stack (PyPI, CRAN, conda-forge, npm): search by task words and by the names publications mention; libraries.io searches across ecosystems at once.
  • Public forges: code search on GitHub/GitLab finds the unregistered majority - search READMEs by domain terms, filter by language and activity, and check the topics/tags of anything close.
  • Curated awesome lists collect a community's known tools; find the list for the domain, then treat it as a lead generator - lists rot, so verify each candidate is alive.
  • Software archives: Software Heritage preserves code whose forge home vanished; JOSS and Zenodo double as software discovery for peer-reviewed and archived tools.
  • Papers with Code links publications to implementations in ML-adjacent fields.

From findings to decisions

Discovery feeds the pack's decision skills rather than replacing them:

  • Candidate software worth adopting goes through the six-axis intake vetting (rseng-dependency-management); fit judgment and citation duty live with rseng-software-reuse.
  • Competitor and alternative surveys become an honest comparison table: what each neighbor does, its stack, license, activity and how the user's project differs - the state-of-the-field material that software papers (rseng-software-peer-review), communication (rseng-science-communication) and documentation's related-projects section (rseng-documentation) all need. Differences stated honestly build more trust than silence about competitors.
  • Everything found gets verified before it is repeated: resolve the DOI, open the repository, confirm the claim matches the source (rseng-fact-checking, rseng-citation-hygiene) - discovery collects leads, verification makes them citable.
  • Record the survey: queries, sources searched, date, and the shortlist with reasons, in the project record (rseng-project-tracking) - a documented search can be updated; an undocumented one gets redone from scratch.

Working with this skill

This skill is source-independent: its authority is the discovery services linked below. It is the front end of a chain: discovery finds, rseng-software-reuse and rseng-dependency-management judge, rseng-fact-checking and rseng-citation-hygiene verify.

Learn more (verified):

<!-- related-skills:begin -->

Related skills

Check whether any of these applies before moving on:

  • rseng-citation-hygiene - verifying surveyed references
  • rseng-dependency-management - vetting discovered software
  • rseng-fact-checking - verifying claims before repeating them
  • rseng-science-communication - related-work narrative for audiences
  • rseng-software-peer-review - state-of-field for JOSS paper
  • rseng-software-reuse - candidate fit and citation duty
<!-- related-skills:end -->

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

コメント

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

送信するとすぐに公開されます。メールアドレスや電話番号などの個人情報は書かないでください。URL は 2 つまでです。

0 / 1000 文字

このフォームは reCAPTCHA で保護されており、Google のプライバシーポリシーと利用規約が適用されます。

同じリポジトリのスキル

Covers operating AI coding agents securely: auditing whether the agent runs sandboxed, permission and dangerous-command configuration, containerized environments, secrets kept out of context, network egress and token privileges, prompt-injection risk, and the privacy of agent use itself. Use PROACTIVELY when permission gating is broadly disabled (skip-permissions modes), when secrets are visible to the agent's shell, or when the agent processes untrusted code, issues or web content; when a project holds personal or confidential data while a cloud agent is active (what leaves the machine, retention, training use), or when the user asks how to run coding agents safely or privately. (Supply-chain security: rseng-security; disclosing agent contributions: rseng-ai-declaration.)

日本語の概要は準備中です。原文の説明を表示しています。

fdiblen/rseng-agent-skills242026年9月23日 更新

Covers declaring AI involvement with the AI Declaration Format (https://ai-declaration.org): creating and maintaining an aidecl.yaml that records which AI tools and agents were used, what each contributed, when and how much, plus the README disclosure footnote, JSON/JSON-LD export and CI validation. Machine-readable disclosure is the practice; this format is one implementation. Use PROACTIVELY when an AI assistant or agent creates or modifies a project's content - generate aidecl.yaml if missing, update it after AI-assisted changes. Also use when the user asks about AI transparency, provenance, disclosure or EU AI Act disclosure, wants to state that NO AI was used, or mentions aidecl. For concealment requests see rseng-honesty; for the human review duty see rseng-human-verification.

日本語の概要は準備中です。原文の説明を表示しています。

fdiblen/rseng-agent-skills242026年9月23日 更新

Covers long-term archiving of research software and data: Software Heritage save requests and SWHID persistent identifiers, Zenodo deposits with versioned DOIs and forge integration, choosing domain and institutional repositories, deciding what to archive (code, data, environments, documentation) and when, and archiving at project retirement. Use when the user wants software or data preserved beyond the life of a forge account, grant or lab, mentions Software Heritage, SWHIDs, Zenodo deposits or archiving, retires or hands over a project, prepares artifacts that must stay resolvable for a paper, or when funder policy requires long-term preservation. (Cutting the release itself is rseng-publishing-releasing; day-to-day data storage and repository choice is rseng-data-management.)

日本語の概要は準備中です。原文の説明を表示しています。

fdiblen/rseng-agent-skills242026年9月23日 更新

Covers processing research data that outgrows one machine's memory: out-of-core and chunked computation, Dask for scaling the scientific Python stack, Spark for distributed tabular pipelines, lazy evaluation, partitioning strategies, idempotent and restartable batch jobs, and knowing when NOT to distribute. Use when datasets no longer fit in memory, when the user mentions Dask, Spark, out-of-core or larger-than-memory data, when a pandas/NumPy workflow hits memory limits, or when designing batch pipelines over many files. (Cluster job submission and job arrays are rseng-hpc-computing; pipeline orchestration engines are rseng-workflows; profile first with rseng-performance-profiling.)

日本語の概要は準備中です。原文の説明を表示しています。

fdiblen/rseng-agent-skills242026年9月23日 更新

Covers continuous integration and delivery for research software: CI/CD concepts, automating builds and tests with GitHub Actions and GitLab CI/CD, and wiring an organization's GitLab CI infrastructure to a GitHub-hosted project. Use when the user asks to set up CI, write a pipeline or workflow file (.github/workflows, .gitlab-ci.yml), add automated builds/tests on push or pull request, publish a package or deploy docs when a tag or release is cut, cache dependencies to speed up CI runs, choose between GitHub Actions and GitLab CI, use self-hosted or GPU runners, mirror a repo, or report external CI status back to GitHub. For what to test and shrinking a test matrix see rseng-testing; for linter and pre-commit policy see rseng-code-quality.

日本語の概要は準備中です。原文の説明を表示しています。

fdiblen/rseng-agent-skills242026年9月23日 更新

Covers verifying that every citation is real, correct and current: checking references in manuscripts, READMEs, references files and code metadata against Crossref and OpenAlex, screening cited DOIs against the Retraction Watch database, catching fabricated or mis-attributed citations (a documented AI failure mode), and keeping bibliographies and CITATION.cff files resolvable. Use PROACTIVELY before any bibliography, reference list or citation metadata is finalized or published, whenever the agent itself has produced citations, and when the user asks to check references, mentions broken DOIs, retracted papers or citation verification, or prepares a manuscript, README or software paper with references. (Making your own software citable is rseng-citation-metadata.)

日本語の概要は準備中です。原文の説明を表示しています。

fdiblen/rseng-agent-skills242026年9月23日 更新

fdiblen のスキルをすべて見る

このスキルの問題を報告する