Creator · JetBrains
Last updated · Aug 24, 2026
writing-specs
Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.
Sandbox only
Install targets
Codex install prompt
Install the "writing-specs" agent skill from https://github.com/JetBrains/thinkrail/tree/main/packages/pi-thinkrail-workflow/skills/writing-specs. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"jetbrains-writing-specs","task":"Install writing-specs","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Research and knowledge work
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
RAG and knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add JetBrains/thinkrail --skill writing-specs
Maintenance
fresh
Pushed today
Risk
Needs review
Low GitHub adoption signal
GitHub quality
38
62/100 Quality · 77/100 Trust
Coverage tags
Review notes
Low GitHub adoption signal · Quality score needs review
Agent adoption scorecard
Trust, audit, and install readiness at a glance
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Human review before install
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
38 GitHub stars
Repo activity
38 stars, 8 forks
Maintenance
Pushed today
License
Apache-2.0
Install
npx skills add JetBrains/thinkrail --skill writing-specs
Install safety
standard package or runtime install path
Permission surface
filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Usable metadata, review docs
Risk summary
Review before production
- Low GitHub adoption signal
- Quality score needs review
- GitHub adoption: 38 GitHub stars
- Stars/forks activity: 38 stars, 8 forks; issue activity unavailable in current metadata
Install readiness
Install path available
- Install path is available
- Repository evidence is available
- License is declared
- No Agent Proven outcome evidence yet
Agent-readable metadata
Machine-readable decision data for this skill.
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
View technical data+
Agent-readable metadata
Machine-readable decision data for this skill.
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
- Coding agents workflows
- Claude Code teams
- builders willing to evaluate younger projects
- Inspect source files
Suited agents
Install decision
- Command
- npx skills add JetBrains/thinkrail --skill writing-specs
- Policy
- review
- Human review
- yes
Trust and risk
- Trust
- 69/100
- Audit
- 79/100
- Risk level
- Needs review
Outcome loop
- Endpoint
- /api/agent/outcome
- Event ID
- resolve
- Outcomes
- 5
Install command
npx skills add JetBrains/thinkrail --skill writing-specsDo not use when
- teams that need a vendor-supported SLA
- production agents without a repository review
- Low GitHub adoption signal
- No OpenAgentSkill engagement data yet
- Quality score needs review
Alternative
Last30days Skill
53.5K Stars
npx skills add mvanhorn/last30days-skill -g
Alternative
Academic Research Skills
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Alternative
GPT Researcher
28.0K Stars
npx skills add assafelovic/gpt-researcher
Alternative
DeepResearch
19.8K Stars
npx skills add Alibaba-NLP/DeepResearch
Agent safety v2
63/100 · Review before install
Usable candidate, but the agent should surface permission and audit notes before installation.
Require human approval before installing into a real workspace.
medium
Network access
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Filesystem access
Skill may read or write project files, documents, generated artifacts, or local workspace state.
- Low GitHub adoption signal
Agent resolve plan
Let an agent verify fit before installing.
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20writing-specs%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20writing-specs%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/jetbrains-writing-specs/install
Agent should check
- Task fit and alternatives from Resolve API.
- Audit score, trust score, and safety policy warnings.
- Install target compatibility for Codex, Claude Code, Cursor, or CLI.
Copy prompt
Task: Use writing-specs in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20writing-specs%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/jetbrains-writing-specs/install
Install command: npx skills add JetBrains/thinkrail --skill writing-specs
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Give an agent the install path, not another directory page.
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/jetbrains-writing-specs/install
LLM text format
/api/skills/jetbrains-writing-specs/install?format=text
Find alternatives
/api/skills/search?q=writing-specs&limit=3
Agent prompt
Use writing-specs for this task. Review https://www.openagentskill.com/api/skills/jetbrains-writing-specs/install, then install with: npx skills add JetBrains/thinkrail --skill writing-specsRegistry metadata
Agent-readable profile for automatic skill selection.
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/jetbrains-writing-specs
LLM text
/api/registry/manifest/jetbrains-writing-specs?format=text
Install alias
/api/registry/install/jetbrains-writing-specs
Recommend
/api/registry/recommend?task=Use%20writing-specs%20in%20an%20agent%20workflow&limit=3
Agent fit
Coding agents
Use-case tags
Platforms
Claude Code
Audit report
Needs review · 79/100
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Fallback candidate for Coding agents
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
Coding agents
Trust label
Prototype first
Install path
Command ready
Use when
- Coding agents workflows
- Claude Code teams
- builders willing to evaluate younger projects
Evidence
- recent repository activity
- install command or GitHub repo available
- 62/100 quality profile
review first
- Low GitHub adoption signal
- No OpenAgentSkill engagement data yet
Implementation path
- 1Install it in a sandbox agent and run one Coding agents task end to end.
- 2Compare output quality, latency, and failure behavior against at least one alternative.
- 3Promote it into production only after reviewing repository permissions, license, and maintenance signals.
Trust profile
Sandbox only
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
CHECK38 GitHub stars
Stars/forks activity
CHECK38 stars, 8 forks; issue activity unavailable in current metadata
Recent maintenance
PASSPushed today
License clarity
PASSApache-2.0
Good signals
- AI review approved
- Install path is available
- Repository evidence is available
- Recently maintained repository
- Install command has no obvious high-risk pattern
- Outcome loop is ready but needs first real agent run
Review before install
- Low GitHub adoption signal
- Quality score needs review
- GitHub adoption: 38 GitHub stars
- Stars/forks activity: 38 stars, 8 forks; issue activity unavailable in current metadata
- No real agent outcome reports yet
- Human review required before unattended installation
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Promising candidate for agent workflows
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Use this skill in these scenarios
Build and ship code
Coding agents
I need a coding agent that can understand a repository, edit code, and review pull requests.
Search private knowledge
RAG and knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Investigate faster
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Workflow fit
Add it to a complete workflow
Turn skills into distribution
Content growth agent
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Inspect, patch, and verify code
Coding review agent
A workflow for software agents that inspect repositories, review pull requests, generate tests, and turn findings into shippable patches.
Ingest, retrieve, and cite
RAG knowledge base
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Alternative shortlist
Compare before you install
Similar skills that may fit this task.
Last30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
GPT Researcher
Run autonomous deep research over web and local sources
DeepResearch
Tongyi Deep Research, the Leading Open-source Deep Research Agent
Overview
--- name: writing-specs description: "Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute." ---
# Writing Specs
The workflow family's shared bar for every spec a workflow produces: **short, honest, on-rails**. Process skills name this concept at the steps that draft or revise specs; *what* to draft and *when* stays with the referencing skill. Graph mechanics — frontmatter, link kinds, the `spec_*` tools — are the spec-graph skill's ground; this concept carries the quality bar the family holds on top of them, and is where the family's rules for specs and the spec graph accrue.
## Short
- Small enough to read in one sitting. Target signal, not completeness. - Explain intent, not inventory: what the thing is for, what it owns, where its boundary runs — never a file listing or a restatement of the code.
## Honest
- Only settled content appears. Never pad with `[TBD]` or placeholder sections — a section that hasn't been settled simply doesn't exist yet. - Anything inferred rather than confirmed is marked unconfirmed, inline, where it stands. - New and inferred specs are `status: draft` until the user has reviewed them — the flip out of `draft` follows the user's review, never the drafting agent's own judgment.
## On-rails
- High-signal enough that a future agent (or human) lands on the decisions without re-deriving them. - The spec is the *only* home for rationale: decisions, invariants, trade-offs, and bug post-mortems are recorded here, never as code comments — a rationale paragraph found in code is content to promote into the owning spec, leaving at most a one-line pointer where misediting would silently break something. - Say each thing once: link by `id` instead of restating; the dependency edges *between* sibling modules live in the parent's spec, not in each leaf. - One spec per *genuine* boundary — not per directory, not per file.
Technical details
- Version
- 1.0.0
- License
- Apache-2.0
- Last updated
- Aug 24, 2026
- Published
- Aug 24, 2026
Decision snapshot
Fallback candidate
recent repository activity
Audit
Install review
Install and adoption review
- Security
- 86/100
- Maintenance
- 100/100
- Install
- 92/100
Agent-proven evidence
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
- Success rate
- —
- Recent failure
- —
- Outcomes
- 0
- Output quality
- —
- Failed
- 0
- Not relevant
- 0
- Installs
- 0
- Risk blocked
- 0
- Setup needed
- 0
- Production
- 0
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Add to agent workflow
Free and open source. Review the report before installing into production agents.
Growth loop
Share kit
Scenario-led draft for writing-specs, ready for a manual X post.
A practical pick for source-backed research: writing-specs: Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — o... 38 stars https://www.openagentskill.com/skills/jetbrains-writing-specs?ref=x
Optional reply with install command
Listing + install path for writing-specs: https://www.openagentskill.com/skills/jetbrains-writing-specs?ref=x Install: npx skills add JetBrains/thinkrail --skill writing-specs
Listing source
Registry indexed
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
- Creator
- JetBrains
- Source
- JetBrains/thinkrail
- Indexed by
- OpenAgentSkill community index
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
Claim this skill listing
This Registry indexed listing is attributed to JetBrains but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Add the evidence badges to your README
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/jetbrains-writing-specs)
[](https://www.openagentskill.com/skills/jetbrains-writing-specs)
[](https://www.openagentskill.com/skills/jetbrains-writing-specs/audit)
[](https://www.openagentskill.com/skills/jetbrains-writing-specs)Author
JetBrains
@jetbrains
Tags
Platform fit
Health signals
- GitHub stars
- 38
- Quality score
- 34/100
- Last GitHub push
- Aug 24, 2026
- Framework hints
- Unknown
- OpenAgentSkill views
- 0
- Install copies
- 0
- Outbound clicks
- 0
Community signal
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Trust & safety
Sandbox only
- GitHub adoption38 GitHub starsCHECK
- Stars/forks activity38 stars, 8 forks; issue activity unavailable in current metadataCHECK
- Recent maintenancePushed todayPASS
- License clarityApache-2.0PASS
- README/SKILL.md completenessPublic metadata needs stronger README/SKILL.md contextINFO
- Dependency/runtime riskno major dependency risk hints in public metadataPASS
Related skills
Last30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
53.5K StarsAcademic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
38.4K StarsGPT Researcher
Run autonomous deep research over web and local sources
28.0K StarsDeepResearch
Tongyi Deep Research, the Leading Open-source Deep Research Agent
19.8K Stars